Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-72479iio: accel: mma8452: handle I2C read error(s) in mma8452_read()

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.

Timeline

  1. ID reserved

    By Linux

  2. · 6 days later

    Published

  3. · 2 days later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.

EPSS (exploitation in 30 days)
0.22% · top 87% of all CVEs (17 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.

Affected products

  • Linux · Linux

    • affected 96c0cb2bbfe0a58bd0c37cf34d50a20f9cd75aa8 – < b488055e81d9faaaf2f8aaff45f9944040ac4493
    • affected 96c0cb2bbfe0a58bd0c37cf34d50a20f9cd75aa8 – < f9ec3f3e9cf27dd06cd3725eeaa44e3ce46be893
    • affected 96c0cb2bbfe0a58bd0c37cf34d50a20f9cd75aa8 – < b4932fc325e84a3233413daf230b043818c8a824
    • affected 96c0cb2bbfe0a58bd0c37cf34d50a20f9cd75aa8 – < eed69f8a10b82989ad732ace0fb43a9fb4e7fe35
    • affected 96c0cb2bbfe0a58bd0c37cf34d50a20f9cd75aa8 – < f3d905ea1e4996d933074481e80d96ecd74a9904
    • affected 96c0cb2bbfe0a58bd0c37cf34d50a20f9cd75aa8 – < 1cddef80a180af74c33d2f26c962ce92b60fded4
    • affected 96c0cb2bbfe0a58bd0c37cf34d50a20f9cd75aa8 – < f3d413e701c5e54bef736b638967724dda880365
    • affected 96c0cb2bbfe0a58bd0c37cf34d50a20f9cd75aa8 – < 5bdff291d20c31b365d9ddfe9c426fbfb41da5bb
  • Linux · Linux

    • affected 4.7
    • unaffected < 4.7
    • unaffected 5.10.261 – ≤ 5.10.*
    • unaffected 5.15.212 – ≤ 5.15.*
    • unaffected 6.1.178 – ≤ 6.1.*
    • unaffected 6.6.145 – ≤ 6.6.*
    • unaffected 6.12.97 – ≤ 6.12.*
    • unaffected 6.18.40 – ≤ 6.18.*
    • unaffected 7.1.5 – ≤ 7.1.*
    • unaffected 7.2 – ≤ *

References

References8

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-72479 badge
[![CVE-2026-72479](https://cveledger.app/badge/CVE-2026-72479.svg)](https://cveledger.app/cve/CVE-2026-72479)

Record last updated .