CVE-2026-80812

UNRATEDCVSS · not yet scoredTrending — 4 sources updated this week
—
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • No CVSS published and no exploitation signals yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS v2: —Exploit: None knownExposed services: Not assessed

No fix is confirmed yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for the fix.

In the Linux kernel, the following vulnerability has been resolved:

ALSA: dummy: Check card index validity at probe

snd_dummy_probe() blindly trusts that the given devptr->id value is within the proper card index range. 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.

CVSS v3
—
EchelonGraph score
Not yet assessedNo source has published severity data for this CVE yet — no CVSS score from NVD or a CNA, no GitHub advisory, and it is not in CISA KEV. This is not a rating of zero; we cannot assess it yet.
EG Score
—
EG Risk
—
EPSS PROB
0.2%
EPSS %ILE
11th
KEV
Not listed

Published

September 4, 2026

Last Modified

September 7, 2026

References (8)

Vendor Advisories for CVE-2026-80812(2)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(4 across 3 ecosystems)
Debian:12(2)
PackageVulnerable rangeFix by version rangeDependents
linux6.1.106-1 ... 6.1.99-1 (56 versions)
  • every version up to 6.1.187-1: fixed in 6.1.187-1
—
linux-6.126.12.100-1~deb12u1, 6.12.101-1~deb12u1
  • every version up to 6.12.107-1~deb12u1: fixed in 6.12.107-1~deb12u1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 6.12.96-1 (34 versions)
  • every version up to 6.12.107-1: fixed in 6.12.107-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 7.1~rc7-1~exp1 (170 versions)
  • every version up to 7.1.12-1: fixed in 7.1.12-1
—

Data Freshness Timeline

(refreshed 11× in last 7d / 41× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-10-04 23:22 UTCEPSS rescore
  2. 2026-10-03 14:26 UTCEPSS rescore
  3. 2026-10-02 17:57 UTCEPSS rescore
  4. 2026-10-02 14:43 UTCVendor advisory
  5. 2026-10-02 14:43 UTCGHSA enrichment
  6. 2026-10-01 19:50 UTCEPSS rescore
  7. 2026-09-30 15:04 UTCEPSS rescore
  8. 2026-09-29 11:49 UTCEG score recompute
  9. 2026-09-29 11:49 UTCVendor advisory
  10. 2026-09-29 11:49 UTCGHSA enrichment
  11. 2026-09-28 13:52 UTCEPSS rescore
  12. 2026-09-27 13:48 UTCEPSS rescore
  13. 2026-09-26 15:59 UTCEPSS rescore
  14. 2026-09-26 08:39 UTCVendor advisory
  15. 2026-09-26 08:39 UTCGHSA enrichment
  16. 2026-09-26 00:28 UTCEPSS rescore
  17. 2026-09-24 14:04 UTCEPSS rescore
  18. 2026-09-23 17:54 UTCEPSS rescore
  19. 2026-09-23 05:20 UTCGHSA enrichment
  20. 2026-09-22 16:01 UTCEPSS rescore
  21. 2026-09-21 21:09 UTCEPSS rescore
  22. 2026-09-20 20:16 UTCEPSS rescore
  23. 2026-09-20 02:33 UTCGHSA enrichment
  24. 2026-09-18 19:28 UTCEPSS rescore
  25. 2026-09-16 23:46 UTCGHSA enrichment
Show 19 more
  1. 2026-09-16 14:08 UTCEPSS rescore
  2. 2026-09-16 05:15 UTCEPSS rescore
  3. 2026-09-15 03:12 UTCEPSS rescore
  4. 2026-09-15 03:12 UTCEPSS rescore
  5. 2026-09-13 20:59 UTCGHSA enrichment
  6. 2026-09-11 14:53 UTCEPSS rescore
  7. 2026-09-11 14:53 UTCEPSS rescore
  8. 2026-09-10 18:11 UTCGHSA enrichment
  9. 2026-09-08 22:01 UTCEPSS rescore
  10. 2026-09-07 15:23 UTCGHSA enrichment
  11. 2026-09-07 15:22 UTCNVD update
  12. 2026-09-07 14:34 UTCEG score recompute
  13. 2026-09-07 14:33 UTCGHSA enrichment
  14. 2026-09-07 14:26 UTCMITRE cvelistV5
  15. 2026-09-06 13:48 UTCEPSS rescore
  16. 2026-09-05 15:31 UTCEPSS rescore
  17. 2026-09-04 16:22 UTCNVD update
  18. 2026-09-04 15:29 UTCEG score recompute
  19. 2026-09-04 15:29 UTCMITRE cvelistV5first tracked

Frequently asked(4)

What is CVE-2026-80812?
CVE-2026-80812 is a publicly disclosed vulnerability published on September 4, 2026. In the Linux kernel, the following vulnerability has been resolved: ALSA: dummy: Check card index validity at probe snddummyprobe() blindly trusts that the given devptr->id value is within the proper card index range. It's OK for the devices the driver itself creates at the module probe time, but…
When was CVE-2026-80812 disclosed?
CVE-2026-80812 was first published on September 4, 2026, with the most recent update on September 7, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-80812 actively exploited?
CVE-2026-80812 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (11th percentile of EPSS-scored CVEs).
How do I remediate CVE-2026-80812?
No fix for CVE-2026-80812 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix. The vendor advisories EchelonGraph has for CVE-2026-80812 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-80812

Explore →

Is Your Infrastructure Affected by CVE-2026-80812?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs