CVE-2026-72479
Last modified
CVE-2026-72479 is a vulnerability of currently unknown severity. 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.. EPSS estimates a 0.21% chance of exploitation in the next 30 days.
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.
Metrics
Affected Software
Source: CNA advisory (CVE.org). NVD analysis pending.
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | >= 96c0cb2bbfe0a58bd0c37cf34d50a20f9cd75aa8, < b488055e81d9faaaf2f8aaff45f9944040ac4493; >= 96c0cb2bbfe0a58bd0c37cf34d50a20f9cd75aa8, < f9ec3f3e9cf27dd06cd3725eeaa44e3ce46be893; >= 96c0cb2bbfe0a58bd0c37cf34d50a20f9cd75aa8, < b4932fc325e84a3233413daf230b043818c8a824; >= 96c0cb2bbfe0a58bd0c37cf34d50a20f9cd75aa8, < eed69f8a10b82989ad732ace0fb43a9fb4e7fe35; >= 96c0cb2bbfe0a58bd0c37cf34d50a20f9cd75aa8, < f3d905ea1e4996d933074481e80d96ecd74a9904; >= 96c0cb2bbfe0a58bd0c37cf34d50a20f9cd75aa8, < 1cddef80a180af74c33d2f26c962ce92b60fded4; >= 96c0cb2bbfe0a58bd0c37cf34d50a20f9cd75aa8, < f3d413e701c5e54bef736b638967724dda880365; >= 96c0cb2bbfe0a58bd0c37cf34d50a20f9cd75aa8, < 5bdff291d20c31b365d9ddfe9c426fbfb41da5bb |
| Linux | Linux | 4.7 |
References
Timeline
- Published
- Last Modified
- Status
- Received
Frequently Asked Questions
What is CVE-2026-72479?
How severe is CVE-2026-72479?
How do I fix CVE-2026-72479?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-72473In the Linux kernel, the following vulnerability has been re…9.8
- CVE-2026-72474In the Linux kernel, the following vulnerability has been re…
- CVE-2026-72475In the Linux kernel, the following vulnerability has been re…
- CVE-2026-72476In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-72477In the Linux kernel, the following vulnerability has been re…9.8
- CVE-2026-72478In the Linux kernel, the following vulnerability has been re…8.4
- CVE-2026-7248A vulnerability was found in D-Link DI-8100 16.07.26A1. This…9.4
- CVE-2026-72480In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-72481In the Linux kernel, the following vulnerability has been re…
- CVE-2026-72482In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-72483In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-72484In the Linux kernel, the following vulnerability has been re…
Are you affected by CVE-2026-72479?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
