CVE-2026-64504: iio: accel: bmc150: clamp the device-reported FIFO frame count
Noroxi assessment
Priority: Monitor (action score 0/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.16% (FIRST EPSS).
- Fixed version: Linux Linux 2fe0531dd73eff1de0f2584cb77716d645e548d5, 35a3cd8fd65e15029eb90f1e510045b1bb071175, 3e766526827acd542bcd36c20c4d5f397e0f6521.
Low priority for now. Upgrade to Linux Linux 2fe0531dd73eff1de0f2584cb77716d645e548d5, 35a3cd8fd65e15029eb90f1e510045b1bb071175, 3e766526827acd542bcd36c20c4d5f397e0f6521 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
In the Linux kernel, the following vulnerability has been resolved: iio: accel: bmc150: clamp the device-reported FIFO frame count __bmc150_accel_fifo_flush() copies the number of samples the device reports in its hardware FIFO into an on-stack buffer u16 buffer[BMC150_ACCEL_FIFO_LENGTH * 3]; which is sized for at most BMC150_ACCEL_FIFO_LENGTH (32) samples. The frame count is read from the FIFO_STATUS register and only masked to its 7 valid bits: count = val & 0x7F; so it can be 0..127. The only other limit applied to it is the optional caller-supplied sample budget: if (samples && count > samples) count = samples; which does not constrain count on the flush-all path (samples == 0), and leaves it well above 32 whenever samples is larger. count samples are then transferred into buffer[]: bmc150_accel_fifo_transfer(data, (u8 *)buffer, count); bmc150_accel_fifo_transfer() reads count * 6 bytes through regmap, so a malfunctioning, malicious or counterfeit accelerometer (or an attacker tampering with the I2C/SPI bus) that reports up to 127 frames writes up to 762 bytes into the 192-byte buffer: a stack out-of-bounds write of up to 570 bytes that clobbers the stack canary, saved registers and the return address. Clamp count to BMC150_ACCEL_FIFO_LENGTH, the number of samples buffer[] is sized for, before the transfer, mirroring the watermark clamp already done in bmc150_accel_set_watermark(). A well-formed flush reports at most BMC150_ACCEL_FIFO_LENGTH frames, so legitimate devices are unaffected.
- Published
- Jul 25, 2026
- Updated
- Aug 17, 2026
- EPSS
- 0.1% · 5th percentile
- CWE
- —
Report tools
Action score
0
Monitor
Low priority for now.
- CVSS
- 0 / 40 · —
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 4.1affected
- 3bbec9773389112330954a6a64422eaa78d546c1 and later · before b5a9f521e0a49a0266200fd535b32a9668ecb33baffected · git
- 3bbec9773389112330954a6a64422eaa78d546c1 and later · before 2fe0531dd73eff1de0f2584cb77716d645e548d5affected · git
- 3bbec9773389112330954a6a64422eaa78d546c1 and later · before d0e6d924a5484e005cae5aff6a0aa07a22f3c9ffaffected · git
- 3bbec9773389112330954a6a64422eaa78d546c1 and later · before bfffc98f3de92e0f76be7c7b72e63ac1776a6dbcaffected · git
- 3bbec9773389112330954a6a64422eaa78d546c1 and later · before 89f4a4ca0ac3a933c750569a771c079a290b0721affected · git
- 3bbec9773389112330954a6a64422eaa78d546c1 and later · before 3e766526827acd542bcd36c20c4d5f397e0f6521affected · git
- 3bbec9773389112330954a6a64422eaa78d546c1 and later · before 35a3cd8fd65e15029eb90f1e510045b1bb071175affected · git
- 3bbec9773389112330954a6a64422eaa78d546c1 and later · before ce0e1cae26096fe959a0da5563a6d6d5a801d5fbaffected · git
- before 4.1not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.180-1 | 6.1.180-1 |
| Debian:12 | linux-6.12 | before 6.12.100-1~deb12u1 | 6.12.100-1~deb12u1 |
| Debian:13 | linux | before 6.12.96-1 | 6.12.96-1 |
| Debian:14 | linux | before 7.1.4-1 | 7.1.4-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2026-64502Jul 25, 2026 · iio: adc: ad_sigma_delta: fix clear_pending_event for registerless devices31Monitor
- ← EarlierCVE-2026-64503Jul 25, 2026 · iio: accel: kxsd9: fix runtime PM imbalance on write_raw() error0Monitor
- Later →CVE-2026-64505Jul 25, 2026 · usb: gadget: function: rndis: add length check for header0Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 2fe0531dd73eff1de0f2584cb77716d645e548d5 | Vendor (CNA) |
| Linux Linux | 35a3cd8fd65e15029eb90f1e510045b1bb071175 | Vendor (CNA) |
| Linux Linux | 3e766526827acd542bcd36c20c4d5f397e0f6521 | Vendor (CNA) |
| Linux Linux | 89f4a4ca0ac3a933c750569a771c079a290b0721 | Vendor (CNA) |
| Linux Linux | b5a9f521e0a49a0266200fd535b32a9668ecb33b | Vendor (CNA) |
| Linux Linux | bfffc98f3de92e0f76be7c7b72e63ac1776a6dbc | Vendor (CNA) |
| Linux Linux | ce0e1cae26096fe959a0da5563a6d6d5a801d5fb | Vendor (CNA) |
| Linux Linux | d0e6d924a5484e005cae5aff6a0aa07a22f3c9ff | Vendor (CNA) |
| debian:linux | 6.1.180-1 · Debian:12 | Package registry (OSV) |
| debian:linux-6.12 | 6.12.100-1~deb12u1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
No CVSS vector for this record, so attack conditions can't be derived.
Weakness class (CWE)
—
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (7 more)Show less
- git.kernel.org/stable/c/35a3cd8fd65e15029eb90f1e510045b1bb071175
- git.kernel.org/stable/c/3e766526827acd542bcd36c20c4d5f397e0f6521
- git.kernel.org/stable/c/89f4a4ca0ac3a933c750569a771c079a290b0721
- git.kernel.org/stable/c/b5a9f521e0a49a0266200fd535b32a9668ecb33b
- git.kernel.org/stable/c/bfffc98f3de92e0f76be7c7b72e63ac1776a6dbc
- git.kernel.org/stable/c/ce0e1cae26096fe959a0da5563a6d6d5a801d5fb
- git.kernel.org/stable/c/d0e6d924a5484e005cae5aff6a0aa07a22f3c9ff
Vendor advisories and official records. Exploit/PoC links are deliberately left out.