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-80969ALSA: mpu401: Check card index validity at probe

Description

In the Linux kernel, the following vulnerability has been resolved: ALSA: mpu401: Check card index validity at probe mpu401 driver blindly trusts that the given devptr->id value is within the proper card index range at probe. It's OK for the devices the driver itself creates at the module probe time, but if the device is bound manually via sysfs interface, this could be -1 as "none", and this leads to OOB access for index[] and other parameters. Add a sanity check for the card index and warn/correct it if it's a value out of the range.

Timeline

  1. ID reserved

    By Linux

  2. · 16 days later

    Published

  3. · 38 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 88% of all CVEs (12 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 b3fe95123f0db79dd0345d249c312823178c11f5 – < 4a3d6c22ca6b6c16e8055fb518aa87f5e043f754
    • affected b3fe95123f0db79dd0345d249c312823178c11f5 – < d606c703d1e0c54996cb3db76a753157cb2a3c06
    • affected b3fe95123f0db79dd0345d249c312823178c11f5 – < 3a997371ac2957f11a033a4cec2930042dadb7e3
    • affected b3fe95123f0db79dd0345d249c312823178c11f5 – < 26a25fb4ef4ba2a33069d489feb75a4c36899cca
    • affected b3fe95123f0db79dd0345d249c312823178c11f5 – < 76b6bc38d0f310c0ae1b2a2ebabe2947d92c601a
    • affected b3fe95123f0db79dd0345d249c312823178c11f5 – < cc4215cc2a4b2a9cf8b1952bbe8d5bf925acb3ea
    • affected b3fe95123f0db79dd0345d249c312823178c11f5 – < 8adda66edf795d4648f8e26f312e4414c535d25a
    • affected b3fe95123f0db79dd0345d249c312823178c11f5 – < f7dcecb92ed192ff5fcf842918fb1aaea84b5bdd
  • Linux · Linux

    • affected 2.6.16
    • unaffected < 2.6.16
    • unaffected 5.10.270 – ≤ 5.10.*
    • unaffected 5.15.221 – ≤ 5.15.*
    • unaffected 6.1.188 – ≤ 6.1.*
    • unaffected 6.6.157 – ≤ 6.6.*
    • unaffected 6.12.109 – ≤ 6.12.*
    • unaffected 6.18.50 – ≤ 6.18.*
    • unaffected 7.2.4 – ≤ 7.2.*
    • unaffected 7.3 – ≤ *

References

References8

Sources

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

Badge for a README or a ticket

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

Record last updated .