Back to CVE records
Not yet scoredPublished Jul 25, 2026

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

Updated under an hour ago ()

Does this affect you?

It affects Linux. Add what you run to find out whether that includes you.

No exploitation reported and no EPSS estimate yet.

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.

CVSS
Not yet scored
Weakness (CWE)
Not given
Known exploited
Not in CISA's KEV catalog
EPSS (exploitation in the next 30 days)
Not loaded for this CVE
Assigned by
Linux
NVD analysis
Received
Record last updated
Aug 17, 2026
First seen by InfoSec Signals
Oct 9, 2026

Affected products

Affected products
Linux Linux
linux:linux (from the name)
from 3bbec9773389112330954a6a64422eaa78d546c1 before b5a9f521e0a49a0266200fd535b32a9668ecb33b; 3bbec9773389112330954a6a64422eaa78d546c1 builds before 2fe0531dd73eff1de0f2584cb77716d645e548d5; from 3bbec9773389112330954a6a64422eaa78d546c1 before d0e6d924a5484e005cae5aff6a0aa07a22f3c9ff; from 3bbec9773389112330954a6a64422eaa78d546c1 before bfffc98f3de92e0f76be7c7b72e63ac1776a6dbc; from 3bbec9773389112330954a6a64422eaa78d546c1 before 89f4a4ca0ac3a933c750569a771c079a290b0721; from 3bbec9773389112330954a6a64422eaa78d546c1 before 3e766526827acd542bcd36c20c4d5f397e0f6521; from 3bbec9773389112330954a6a64422eaa78d546c1 before 35a3cd8fd65e15029eb90f1e510045b1bb071175; from 3bbec9773389112330954a6a64422eaa78d546c1 before ce0e1cae26096fe959a0da5563a6d6d5a801d5fb
CNA record

References

References

The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.

Your cookie choices
We use essential cookies to run this site, and, only with your consent, an advertising cookie from Google to measure whether our ads lead to sign-ups and subscriptions. See our for details.