CVE-2026-80973

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

A fix is available — apply it.

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

ALSA: 6fire: bound the MIDI event length from the device

usb6fire_comm_receiver_handler() forwards a MIDI event using a length byte the device supplies, with no bound and no check that the transfer delivered that many bytes:

if (!urb->status) { if (rt->receiver_buffer[0] == 0x10) /* midi in event */ if (midi_rt) midi_rt->in_received(midi_rt, rt->receiver_buffer + 2, rt->receiver_buffer[1]); }

receiver_buffer is a 64-byte kzalloc() buffer (COMM_RECEIVER_BUFSIZE), so only 62 bytes follow the two-byte header. receiver_buffer[1] is a u8 the device chooses, so a device that answers with 0x10 and a length of 0xFF makes snd_rawmidi_receive() read 255 bytes starting two bytes into a 64-byte object. The bytes past the buffer are handed to userspace through the rawmidi read path.

urb->actual_length is not consulted either, so a short transfer leaves both the type byte and the length byte at their previous values and the handler acts on stale data.

The receiver URB is submitted from usb6fire_comm_init() at probe, so the read happens on plug with no user action; forwarding to userspace also needs a MIDI input substream open, since usb6fire_midi_in_received() only calls snd_rawmidi_receive() when rt->in is set.

KASAN on 7.2.0-rc5 (arm64), single packet from an emulated device:

BUG: KASAN: slab-out-of-bounds in snd_rawmidi_receive Read of size 255 at addr ffff000009f64682 by task bash/183 __asan_memcpy snd_rawmidi_receive usb6fire_midi_in_received [snd_usb_6fire] usb6fire_comm_receiver_handler [snd_usb_6fire] Allocated by task 11: usb6fire_comm_init [snd_usb_6fire] usb6fire_chip_probe [snd_usb_6fire] The buggy address is located 2 bytes inside of allocated 64-byte region [ffff000009f64680, ffff000009f646c0)

Reject the event when the length exceeds the bytes that follow the header, and require the transfer to have delivered the header plus that many bytes. The receiver URB is submitted with a 64-byte transfer_buffer_length, so a genuine device cannot deliver an event longer than those 62 bytes and nothing valid is dropped.

Discovered by XBOW, triaged by Baul Lee

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

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). Where an input reads “CISA's BOD 26-04 default”, no one has published it for this CVE, and CISA's implementation guidance says: “If “Automatable” and “Technical Impact” information items about a CVE ID are not available and the CVE ID is not in the KEV Catalog, CISA will treat its values as “no” and “total,” respectively, until CISA or a third party provides metadata about the CVE ID. CISA will always provide the Vulnrichment data for a CVE ID listed in the KEV Catalog.” Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

September 11, 2026

Last Modified

September 14, 2026

Vendor Advisories for CVE-2026-80973(1)

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 ... 7.2~rc7-1~exp1 (360 versions)
  • every version on: no fix on record
—
linux-6.126.12.100-1~deb12u1, 6.12.101-1~deb12u1, 6.12.107-1~deb12u1
  • every version up to 6.12.111-1~deb12u1: fixed in 6.12.111-1~deb12u1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 6.12.96-1 (35 versions)
  • every version up to 6.12.111-1: fixed in 6.12.111-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 7.2~rc7-1~exp1 (179 versions)
  • every version up to 7.2.6-1: fixed in 7.2.6-1
—

All Vendor Advisories

(1)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 15× in last 7d / 55× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 1 repeat row among the latest 59 is merged into the row it repeats.

  1. 2026-10-13 16:35 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  2. 2026-10-12 16:35 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  3. 2026-10-12 14:57 UTCEG score recompute
  4. 2026-10-11 19:21 UTCEG score recompute
  5. 2026-10-11 16:37 UTCEG score recompute
  6. 2026-10-11 13:55 UTCEG score recompute
  7. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  8. 2026-10-11 10:02 UTCVendor advisory
  9. 2026-10-11 10:02 UTCGHSA enrichmentGHSA-xqvm-46mc-2mf2
  10. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  11. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  12. 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  13. 2026-10-08 08:33 UTCVendor advisory
  14. 2026-10-08 08:33 UTCGHSA enrichmentGHSA-xqvm-46mc-2mf2
  15. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  16. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  17. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  18. 2026-10-05 09:21 UTCVendor advisory
  19. 2026-10-05 09:21 UTCGHSA enrichmentGHSA-xqvm-46mc-2mf2
  20. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  21. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  22. 2026-10-02 17:57 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  23. 2026-10-02 10:04 UTCVendor advisory
  24. 2026-10-02 10:04 UTCGHSA enrichmentGHSA-xqvm-46mc-2mf2
  25. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.2% · 11th percentile
Show 33 more
  1. 2026-09-30 15:04 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  2. 2026-09-29 10:52 UTCEG score recompute
  3. 2026-09-29 10:52 UTCVendor advisory
  4. 2026-09-29 10:52 UTCGHSA enrichmentGHSA-xqvm-46mc-2mf2
  5. 2026-09-28 13:52 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  6. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  7. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  8. 2026-09-26 10:48 UTCVendor advisory
  9. 2026-09-26 10:47 UTCGHSA enrichmentGHSA-xqvm-46mc-2mf2
  10. 2026-09-26 00:28 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  11. 2026-09-24 14:04 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  12. 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  13. 2026-09-23 11:28 UTCVendor advisory
  14. 2026-09-23 11:28 UTCGHSA enrichmentGHSA-xqvm-46mc-2mf2
  15. 2026-09-22 16:01 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  16. 2026-09-21 21:09 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  17. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  18. 2026-09-20 12:15 UTCVendor advisory
  19. 2026-09-20 12:15 UTCGHSA enrichmentGHSA-xqvm-46mc-2mf2
  20. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  21. 2026-09-17 12:58 UTCVendor advisory
  22. 2026-09-17 12:58 UTCGHSA enrichmentGHSA-xqvm-46mc-2mf2
  23. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  24. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  25. 2026-09-15 03:12 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  26. 2026-09-14 13:35 UTCGHSA enrichmentGHSA-xqvm-46mc-2mf2
  27. 2026-09-14 13:27 UTCNVD update
  28. 2026-09-14 12:32 UTCEG score recompute
  29. 2026-09-14 12:32 UTCGHSA enrichmentGHSA-xqvm-46mc-2mf2
  30. 2026-09-14 12:24 UTCMITRE cvelistV5
  31. 2026-09-11 20:36 UTCNVD update
  32. 2026-09-11 19:53 UTCEG score recompute
  33. 2026-09-11 19:49 UTCMITRE cvelistV5first tracked

Frequently asked(4)

What is CVE-2026-80973?
CVE-2026-80973 is a vulnerability whose severity is not yet rated; its CVE record was published on September 11, 2026. In the Linux kernel, the following vulnerability has been resolved: ALSA: 6fire: bound the MIDI event length from the device usb6firecommreceiver_handler() forwards a MIDI event using a length byte the device supplies, with no bound and no check that the transfer delivered that many bytes: if…
When was the CVE record for CVE-2026-80973 published?
The CVE record for CVE-2026-80973 was published on September 11, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of September 14, 2026; the record at its source may have been updated since.
Is CVE-2026-80973 actively exploited?
CVE-2026-80973 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-80973?
A fix for CVE-2026-80973 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-80973 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-80973

Explore →

Is Your Infrastructure Affected by CVE-2026-80973?

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