CVE-2026-64495 — iio: gyro: bmg160: bail out when bandwidth/filter is not in table
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.
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- No scoring signals.
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (Linux Linux).
- No fix documented in the sources: reduce exposure and monitor the vendor advisory.
- Search available logs for exploit probes, errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| Linux | Linux |
≥ 22b46c45fb9be8ec1fcb4d9b74810e6a20ff67cc and < 1dc3a833be11e5d503038e3c701745fd0e03903c≥ 22b46c45fb9be8ec1fcb4d9b74810e6a20ff67cc and < 77e56ebb1786f4296afd5fa46975a989b285ae65≥ 22b46c45fb9be8ec1fcb4d9b74810e6a20ff67cc and < 029481cddb98697716f4bf3021d035eaf2ca0e1f≥ 22b46c45fb9be8ec1fcb4d9b74810e6a20ff67cc and < 8d202515baea4e2e3be448d1590099af28f2346d≥ 22b46c45fb9be8ec1fcb4d9b74810e6a20ff67cc and < d85ee50f58dd83fe74f6d0bf8bd345c657b216e8≥ 22b46c45fb9be8ec1fcb4d9b74810e6a20ff67cc and < 7bbf02b63961fc1768c9c654392c11f2077d4c59≥ 22b46c45fb9be8ec1fcb4d9b74810e6a20ff67cc and < 6c8675468862161d1c59130266852b66867d3861≥ 22b46c45fb9be8ec1fcb4d9b74810e6a20ff67cc and < 8320c77e67382d5d55d77043a5f60a867d408a2b and 1 moreversion 3.18 |
Vulnerable | CVE Program (cve.org) e CISA ADP |
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Not enough vector or weakness data: use the affected application’s logs as a starting point.
Timeline
What happened to this CVE, newest first.
- 2026
- Record published
- Affected products added · linux/linux
- Source status changed · → Received
- Record created in this database
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 1× Official description updated · Oct 15, 2026 – Oct 15, 2026
References
8 on the record
- git.kernel.org/stable/c/77e56ebb1786f4296afd5fa46975a989b285ae65
- git.kernel.org/stable/c/029481cddb98697716f4bf3021d035eaf2ca0e1f
- git.kernel.org/stable/c/7bbf02b63961fc1768c9c654392c11f2077d4c59
- git.kernel.org/stable/c/6c8675468862161d1c59130266852b66867d3861
- git.kernel.org/stable/c/1dc3a833be11e5d503038e3c701745fd0e03903c
- git.kernel.org/stable/c/d85ee50f58dd83fe74f6d0bf8bd345c657b216e8
- git.kernel.org/stable/c/8320c77e67382d5d55d77043a5f60a867d408a2b
- git.kernel.org/stable/c/8d202515baea4e2e3be448d1590099af28f2346d
Elsewhere on this site
Related CVEs (same products)
- Critical CVE-2026-99999 ipv4: validate checksum_start before completing checksum 12h
- Unknown CVE-2026-98432 ipv4: free inet_opt and ireq_opt after an RCU grace period 12h
- Unknown CVE-2026-98428 ALSA: usb: 6fire: Avoid embedded URBs 1d
- Unknown CVE-2026-98431 RDMA/uverbs: Fix mmap_lock/disassociation_lock circular dependency 1d
- Unknown CVE-2026-98430 RDMA/efa: Keep admin queues alive while IRQ is registered 1d
- Unknown CVE-2026-98429 RDMA/efa: Keep EQ resources alive while IRQ is registered 1d
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No CVSS score published by NVD, the CNA, CISA or GitHub so far.
- No FIRST EPSS score.
- No fixed version, patch or mitigation documented.
- No CISA SSVC assessment.
- No CWE classification.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2026-64495 is "iio: gyro: bmg160: bail out when bandwidth/filter is not in table", rated Unknown. It affects Linux (Linux); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.