# CVE-2026-64495: iio: gyro: bmg160: bail out when bandwidth/filter is not in table

> A local attacker can trigger an out-of-bounds read in the BMG160 gyro driver via sysfs, potentially causing a kernel crash or leaking memory.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 25 Jul 2026
- **Updated:** 17 Aug 2026
- **Also known as:** BELL-CVE-2026-64495, DEBIAN-CVE-2026-64495, GHSA-w643-8cr7-vjmg, ROOT-OS-UBUNTU-2204-CVE-2026-64495, UBUNTU-CVE-2026-64495

## What is CVE-2026-64495?

CVE-2026-64495 is a memory corruption vulnerability in Linux, published on 25 Jul 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: gyro: bmg160: bail out when bandwidth/filter is not in table

bmg160_get_filter() walks bmg160_samp_freq_table[] looking for the entry
matching the bw_bits value read from the chip:

	for (i = 0; i < ARRAY_SIZE(bmg160_samp_freq_table); ++i) {
		if (bmg160_samp_freq_table[i].bw_bits == bw_bits)
			break;
	}
	*val = bmg160_samp_freq_table[i].filter;

If no entry matches, i ends up equal to the array size and the next line
reads one slot past the end. bmg160_set_filter() has the same shape, driven
by 'val' instead of bw_bits.

smatch flags both:

  drivers/iio/gyro/bmg160_core.c:204 bmg160_get_filter() error:
  buffer overflow 'bmg160_samp_freq_table' 7 <= 7
  drivers/iio/gyro/bmg160_core.c:222 bmg160_set_filter() error:
  buffer overflow 'bmg160_samp_freq_table' 7 <= 7

Return -EINVAL when no entry matches.

The set_filter() path is reachable from userspace via the sysfs
in_anglvel_filter_low_pass_3db_frequency interface, so userspace can
trivially trigger the out-of-bounds read with a value that is not in
bmg160_samp_freq_table[].filter.

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


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

Apply the vendor's patch.

## Is CVE-2026-64495 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-64495 is a memory corruption vulnerability in Linux, published on 25 Jul 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-64495 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-64495/ (Markdown: https://insights.sbomify.com/CVE-2026-64495/index.md)
```

## Sources

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

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