# CVE-2026-98658: iio: proximity: aw96103: validate firmware data length

> A missing length validation in the aw96103 proximity sensor driver allows out-of-bounds reads via crafted firmware, potentially causing crashes or information disclosure.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 18 Oct 2026
- **Updated:** 19 Oct 2026
- **Also known as:** BELL-CVE-2026-98658, DEBIAN-CVE-2026-98658, GHSA-h95c-5qhw-xc7v, UBUNTU-CVE-2026-98658

## What is CVE-2026-98658?

CVE-2026-98658 is a vulnerability in Linux, published on 18 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

In the Linux kernel, the following vulnerability has been resolved:

iio: proximity: aw96103: validate firmware data length

The firmware parser reads a length from the binary header and then uses
it to walk six-byte register/value entries. A truncated firmware image
can make the parser read beyond the copied firmware buffer. A value
smaller than the four-byte count field also underflows, producing a very
large length.

Read the little-endian field with get_unaligned_le32(), as previously
proposed by David Lechner. Validate the header size, reject an
underflowed length, ensure the resulting payload is contained in the
firmware image, and require it to contain whole register/value entries.

## Which versions are affected by CVE-2026-98658?


## How do I fix CVE-2026-98658?

Apply the vendor's patch.

## Is CVE-2026-98658 being exploited?

There is no known exploitation of CVE-2026-98658 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-98658 and fix it if it is affected.

What it is: CVE-2026-98658 is a vulnerability in Linux, published on 18 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-98658 in the wild and no public exploit code.

Affected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-98658/ (Markdown: https://insights.sbomify.com/CVE-2026-98658/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-98658
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-98658
- OSV: https://osv.dev/vulnerability/CVE-2026-98658

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-98658/
Summaries are generated and may contain mistakes; the official description above is the record.