CVE-2026-72479

iio: accel: mma8452: handle I2C read error(s) in mma8452_read()

N/A

Published: August 15, 2026 at 05:57 AM UTC

Updated: August 17, 2026 at 06:19 AM UTC

1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available

Start Free Sign In

Severity

N/A

Exploit prediction

EPSS 0.2%

Description

In the Linux kernel, the following vulnerability has been resolved: iio: accel: mma8452: handle I2C read error(s) in mma8452_read() Currently, If i2c_smbus_read_i2c_block_data() fails but mma8452_set_runtime_pm_state() succeeds, mma8452_read() returns 0. As a result, the caller mma8452_read_raw() assumes the read was successful and proceeds to use a buffer containing uninitialized stack memory. Add proper checking of the I2C read return value and propagate errors to the caller.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

Linux Kernel · Linux

95%

4.7 ≤ v < 5.10.2614.7 ≤ v < 5.15.2124.7 ≤ v < 6.1.1784.7 ≤ v < 6.12.974.7 ≤ v < 6.18.404.7 ≤ v < 6.6.1454.7 ≤ v < 7.1.54.7 ≤ v < 7.24.796c0cb2bbfe0a58bd0c37cf34d50a20f9cd75aa8

Vendor states this is fixed in 1cddef80a180af74c33d2f26c962ce92b60fded4 (fixed)

Vendor states this is fixed in 5bdff291d20c31b365d9ddfe9c426fbfb41da5bb (fixed)

Vendor states this is fixed in b488055e81d9faaaf2f8aaff45f9944040ac4493 (fixed)

Vendor states this is fixed in b4932fc325e84a3233413daf230b043818c8a824 (fixed)

Vendor states this is fixed in eed69f8a10b82989ad732ace0fb43a9fb4e7fe35 (fixed)

Vendor states this is fixed in f3d413e701c5e54bef736b638967724dda880365 (fixed)

Vendor states this is fixed in f3d905ea1e4996d933074481e80d96ecd74a9904 (fixed)

Vendor states this is fixed in f9ec3f3e9cf27dd06cd3725eeaa44e3ce46be893 (fixed)

Vendor states this is fixed in 4.7 (unaffected)

Vendor states this is fixed in 5.10.261 (unaffected)

Vendor states this is fixed in 5.15.212 (unaffected)

Vendor states this is fixed in 6.1.178 (unaffected)