CVE-2026-80872

UNRATEDCVSS · not yet scoredTrending — 3 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%CVSS v2: —Exploit: None knownExposed: 0

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

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

ALSA: hda/tas2781: Cancel async firmware request at unbind

TAS2781 HDA I2C and SPI queue RCA firmware loading from component bind with request_firmware_nowait(). The firmware loader keeps the callback module pinned and holds a device reference, but the callback still uses driver-private HDA state.

Component unbind removes controls and DSP state immediately. Later device removal tears down the TAS2781 private data, including codec_lock. If the async firmware callback runs after unbind has started, it can operate on state that is being torn down.

Cancel or synchronize the async firmware request before removing controls and DSP state. A queued callback is cancelled, and an already-running callback is allowed to finish before unbind continues.

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%
EPSS %ILE
5%
KEV
Not listed

Published

September 4, 2026

Last Modified

September 4, 2026

References (3)

Vendor Advisories for CVE-2026-80872(2)

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

Affected Packages

(2 across 2 ecosystems)
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.2~rc7-1~exp1 (176 versions)——
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.1~rc7-1~exp1 (159 versions)7.1.5-1—

Data Freshness Timeline

(refreshed 9× in last 7d / 20× 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-09-18 19:28 UTCEPSS rescore
  2. 2026-09-17 02:16 UTCVendor advisory
  3. 2026-09-17 02:16 UTCGHSA enrichment
  4. 2026-09-16 14:08 UTCEPSS rescore
  5. 2026-09-16 05:15 UTCEPSS rescore
  6. 2026-09-15 03:12 UTCEPSS rescore
  7. 2026-09-15 03:12 UTCEPSS rescore
  8. 2026-09-14 00:04 UTCVendor advisory
  9. 2026-09-14 00:04 UTCGHSA enrichment
  10. 2026-09-11 14:53 UTCEPSS rescore
  11. 2026-09-11 14:53 UTCEPSS rescore
  12. 2026-09-10 21:52 UTCGHSA enrichment
  13. 2026-09-07 19:38 UTCEG score recompute
  14. 2026-09-07 19:38 UTCVendor advisory
  15. 2026-09-07 19:38 UTCGHSA enrichment
  16. 2026-09-06 13:48 UTCEPSS rescore
  17. 2026-09-05 15:31 UTCEPSS rescore
  18. 2026-09-04 17:24 UTCNVD update
  19. 2026-09-04 16:55 UTCEG score recompute
  20. 2026-09-04 16:54 UTCMITRE cvelistV5first tracked

Frequently asked(4)

What is CVE-2026-80872?
CVE-2026-80872 is a publicly disclosed vulnerability published on September 4, 2026. In the Linux kernel, the following vulnerability has been resolved: ALSA: hda/tas2781: Cancel async firmware request at unbind TAS2781 HDA I2C and SPI queue RCA firmware loading from component bind with requestfirmwarenowait(). The firmware loader keeps the callback module pinned and holds a device…
When was CVE-2026-80872 disclosed?
CVE-2026-80872 was first published in the National Vulnerability Database on September 4, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-80872 actively exploited?
CVE-2026-80872 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 95.0% of all scored CVEs.
How do I remediate CVE-2026-80872?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-80872, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-80872?

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

Start Free Scan →Browse All CVEs