# CVE-2026-98660: iio: pressure: bmp280: fix out-of-bounds access in sampling frequency lookup

> A local attacker can trigger an out-of-bounds read in the BMP280 pressure sensor driver, potentially causing a system crash or leaking kernel memory.

- **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:** 21 Oct 2026
- **Also known as:** AZL-109067, BELL-CVE-2026-98660, DEBIAN-CVE-2026-98660, GHSA-mpqw-8x9x-wfxf, UBUNTU-CVE-2026-98660

## What is CVE-2026-98660?

CVE-2026-98660 is a memory corruption 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: pressure: bmp280: fix out-of-bounds access in sampling frequency lookup

The sampling frequency tables store each frequency as an integer part and
a fractional part in micro units. num_sampling_freq_avail is initialized
to the number of flattened integer elements because read_avail() returns
the table as a flat array.

bmp280_write_sampling_frequency(), however, indexes the same table as a
two-dimensional array and uses num_sampling_freq_avail as the number of
rows. Convert the flattened element count back to the number of rows
before iterating over the table.

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


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

Apply the vendor's patch.

## Is CVE-2026-98660 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-98660 is a memory corruption 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-98660 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-98660/ (Markdown: https://insights.sbomify.com/CVE-2026-98660/index.md)
```

## Sources

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

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