VulnerabilityPublished 25 Jul 2026Updated 17 Aug 2026

CVE-2026-64504: Linux kernel · iio: accel: bmc150: clamp the device-reported FIFO frame count

Affects Linux kernelSource GCVE Database

Compare

Not known to be exploited.

Data as of 3 Nov 2026, 18:44 UTC

Severity

High

Rated High by Threat Radar's AI analysis · No CVSS score from NVD or the CNA

Thin evidence

One scorer or none

Exploitation evidence

Disclosed: evidence found.
CVE published 25 Jul 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 3 Nov 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

AI-suggested

Apply the official patch that clamps the FIFO frame count to the buffer size before data transfer, preventing out-of-bounds writes. Until patched, avoid using untrusted or counterfeit accelerometer devices and secure the I2C/SPI bus against tampering. Since this is a kernel vulnerability, update the Linux kernel to a version that includes this fix once available.

Description

A vulnerability in the Linux kernel's bmc150 accelerometer driver allows a stack out-of-bounds write due to improper clamping of the FIFO frame count reported by the device. The driver allocates a fixed-size buffer for up to 32 samples but may process up to 127 samples if the device reports a higher count, leading to potential memory corruption. This flaw can be triggered by a malfunctioning, malicious, or counterfeit accelerometer or by an attacker tampering with the I2C/SPI bus. The issue is resolved by clamping the frame count to the buffer size before data transfer, ensuring legitimate devices are unaffected.

Impact

A stack out-of-bounds write vulnerability exists that can lead to memory corruption in kernel space. This may allow an attacker with control over the accelerometer device or the I2C/SPI bus to overwrite critical stack data, including the stack canary and return address, potentially resulting in privilege escalation or kernel crashes. No known exploits in the wild have been reported.

Summary

The Linux kernel's bmc150 accelerometer driver (__bmc150_accel_fifo_flush) copies samples from the device's hardware FIFO into a fixed-size on-stack buffer sized for 32 samples. The frame count is read from the FIFO_STATUS register and masked to 7 bits, allowing values up to 127. Without proper clamping, the driver may transfer up to 127 frames (762 bytes) into a 192-byte buffer, causing a stack out-of-bounds write of up to 570 bytes. This can overwrite the stack canary, saved registers, and return address, potentially enabling code execution or kernel crashes. The fix clamps the frame count to the buffer size (32 samples) before transfer, mirroring existing watermark clamping logic. Legitimate devices report at most 32 frames, so normal operation is unaffected.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Description

AI analysisMachine-generated, updated 3 Nov 2026, 18:44 UTC

Technical details

References

Community reviews

Related threats