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-72481iio: magnetometer: ak8975: fix potential kernel stack memory leak

Description

In the Linux kernel, the following vulnerability has been resolved: iio: magnetometer: ak8975: fix potential kernel stack memory leak Currently in the AK8975 driver there are four instances where potential uninitialized kernel stack memory leaks can occur. If i2c_smbus_read_i2c_block_data_or_emulated() returns a value less than the size of the buffer, uninitialized bytes are retained in the buffer and later the buffer is passed on to IIO buffers, potentially leaking memory to userspace. Fix this by adding checks whether the return value of the function is equal to the size of the buffer and subsequently if the value is lesser than zero to distinguish from a returned error code.

Timeline

  1. ID reserved

    By Linux

  2. · 6 days later

    Published

  3. · 3 months 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 (19 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
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 bc11ca4a0b84a2f2ebaca2614b92998738d13b1e – < 12848f4ded022963944c063e09a192549a4dad1e
    • affected bc11ca4a0b84a2f2ebaca2614b92998738d13b1e – < a9cf46054f81972f8c0f1dc2a79d2a141999dbce
    • affected bc11ca4a0b84a2f2ebaca2614b92998738d13b1e – < 9f920550abacedc7fc3163dea65ac2a7d0b0765d
    • affected bc11ca4a0b84a2f2ebaca2614b92998738d13b1e – < 8cf346074533356d67a6a6a43a192328ad341f11
    • affected bc11ca4a0b84a2f2ebaca2614b92998738d13b1e – < b974566803bceb72f0b9b5f1d7270b79ba963766
    • affected bc11ca4a0b84a2f2ebaca2614b92998738d13b1e – < 3d57672119525c59ed73ea21accb001ccbcd6cfd
    • affected bc11ca4a0b84a2f2ebaca2614b92998738d13b1e – < fb27ebf81136e796c7b719303ef6fd7e1ae5d488
    • affected bc11ca4a0b84a2f2ebaca2614b92998738d13b1e – < a9a00d727b7bbc5e913a919530a9dd468935bf95
  • 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-72481 badge
[![CVE-2026-72481](https://cveledger.app/badge/CVE-2026-72481.svg)](https://cveledger.app/cve/CVE-2026-72481)

Record last updated .