CVE-2026-74499

UNRATEDCVSS · not yet scoredTrending — 5 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: usb-audio: fix OOB write in snd_usbmidi_akai_output()

snd_usbmidi_akai_output() computes its fill-loop bound

buf_end = ep->max_transfer - MAX_AKAI_SYSEX_LEN - 1;

as a signed int, so a small device-advertised bulk-OUT max_transfer makes buf_end negative. The loop guard then compares the u32 urb->transfer_buffer_length against that negative int: the usual arithmetic conversion turns buf_end into a large unsigned value, so the guard stays true and each iteration keeps appending SysEx framing and payload bytes past the end of the URB transfer buffer, which is only max_transfer bytes long.

A USB device that advertises a tiny bulk-OUT endpoint can therefore trigger an attacker-length- and content-controlled heap out-of-bounds write when a process writes to the created /dev/snd/midiC*D* node.

Return early when there is no room for even one SysEx, so the loop is never entered with a bound that would wrap. The loop is the last statement of the function, so bailing out is equivalent to it not running.

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

Published

August 15, 2026

Last Modified

August 19, 2026

Vendor Advisories for CVE-2026-74499(1)

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

Data Freshness Timeline

(refreshed 19× in last 7d / 19× 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-08-20 22:56 UTCEPSS rescore
  2. 2026-08-19 17:38 UTCGHSA enrichment
  3. 2026-08-19 17:34 UTCNVD update
  4. 2026-08-19 17:04 UTCEPSS rescore
  5. 2026-08-19 16:53 UTCGHSA enrichment
  6. 2026-08-19 16:52 UTCMITRE cvelistV5
  7. 2026-08-18 13:49 UTCEPSS rescore
  8. 2026-08-18 13:49 UTCEPSS rescore
  9. 2026-08-17 13:47 UTCEPSS rescore
  10. 2026-08-17 06:24 UTCGHSA enrichment
  11. 2026-08-17 06:23 UTCNVD update
  12. 2026-08-17 05:40 UTCEG score recompute
  13. 2026-08-17 05:40 UTCGHSA enrichment
  14. 2026-08-17 05:39 UTCMITRE cvelistV5
  15. 2026-08-16 14:56 UTCEPSS rescore
  16. 2026-08-16 14:56 UTCEPSS rescore
  17. 2026-08-15 13:27 UTCNVD update
  18. 2026-08-15 12:39 UTCEG score recompute
  19. 2026-08-15 12:37 UTCMITRE cvelistV5first tracked

Frequently asked(4)

What is CVE-2026-74499?
CVE-2026-74499 is a publicly disclosed vulnerability published on August 15, 2026. In the Linux kernel, the following vulnerability has been resolved: ALSA: usb-audio: fix OOB write in sndusbmidiakai_output() sndusbmidiakai_output() computes its fill-loop bound bufend = ep->maxtransfer - MAXAKAISYSEX_LEN - 1; as a signed int, so a small device-advertised bulk-OUT max_transfer…
When was CVE-2026-74499 disclosed?
CVE-2026-74499 was first published in the National Vulnerability Database on August 15, 2026, with the most recent update on August 19, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-74499 actively exploited?
CVE-2026-74499 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 92.5% of all scored CVEs.
How do I remediate CVE-2026-74499?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-74499, 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

Explore the affected products and dependency analysis for CVE-2026-74499

Explore →

Is Your Infrastructure Affected by CVE-2026-74499?

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