CVE-2026-74501ALSA: usb-audio: fix use-after-free in ump_to_endpoint()
- —Not scoredno CVSS score yet
- 0.17%Exploitation in 30 daysEPSS · top 94% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
Description
In the Linux kernel, the following vulnerability has been resolved: ALSA: usb-audio: fix use-after-free in ump_to_endpoint() create_midi2_ump() registers a card-owned snd_ump_endpoint and stores a back-pointer to its per-interface snd_usb_midi2_ump object in ump->private_data, but it never installs an ump->private_free hook and never clears that pointer. If a later step of snd_usb_midi_v2_create() fails, its error path calls free_all_midi2_umps(), which kfree()s the snd_usb_midi2_ump object while the already-registered endpoint keeps pointing at it. The created /dev/snd/umpC*D* node stays exposed, so the first operation of any UMP open, ump_to_endpoint(), dereferences the dangling ump->private_data and reads rmidi->eps[dir] out of freed memory. A malicious USB MIDI 2.0 device that makes creation fail after the endpoint is registered can thus trigger a slab use-after-free read on a subsequent open of the UMP node. Clear the endpoint's back-pointer before freeing the object, and let ump_to_endpoint() tolerate a NULL private_data so the open/close/trigger callbacks fail cleanly (their callers already handle a NULL endpoint) instead of dereferencing a stale pointer. Discovered by XBOW, triaged by Baul Lee <[email protected]>
Timeline
ID reserved
By Linux
Published
- 2 days later
· 2 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.17% · top 94% of all CVEs (12 Nov 2026)
The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.
Affected products
- affected ff49d1df79aef7580fe3ac99d17c3f886655d080 – < 49eccef6d6e1c00dac6fb2e7eb6f9206c33e1c37
- affected ff49d1df79aef7580fe3ac99d17c3f886655d080 – < 8a7a33b846d6ba695891b8d0040027cdbad8cd52
- affected ff49d1df79aef7580fe3ac99d17c3f886655d080 – < cc014ebf803174f0e5d15956dfc5a38413c945ae
- affected ff49d1df79aef7580fe3ac99d17c3f886655d080 – < ae388c0e1bf727972096f770f82d12e4f748d1b6
- affected ff49d1df79aef7580fe3ac99d17c3f886655d080 – < 4a05b2d1b4642df74f30b6f54843e825c4a2bfd3
- affected 6.5
- unaffected < 6.5
- unaffected 6.6.151 – ≤ 6.6.*
- unaffected 6.12.103 – ≤ 6.12.*
- unaffected 6.18.44 – ≤ 6.18.*
- unaffected 7.1.8 – ≤ 7.1.*
- unaffected 7.2 – ≤ *
References
References5
- https://git.kernel.org/stable/c/49eccef6d6e1c00dac6fb2e7eb6f9206c33e1c37 (opens in a new tab)
- https://git.kernel.org/stable/c/8a7a33b846d6ba695891b8d0040027cdbad8cd52 (opens in a new tab)
- https://git.kernel.org/stable/c/cc014ebf803174f0e5d15956dfc5a38413c945ae (opens in a new tab)
- https://git.kernel.org/stable/c/ae388c0e1bf727972096f770f82d12e4f748d1b6 (opens in a new tab)
- https://git.kernel.org/stable/c/4a05b2d1b4642df74f30b6f54843e825c4a2bfd3 (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2026-59694 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2026-74501)Record last updated .