Skip to content
Threat Brief

← All advisories

CVE-2026-99318

High 7.8No known exploitationFix available

ALSA: bcd2000: Fix use-after-free of MIDI URBs on file close

Record last updated

CVSS score

7.8

High on a 0 to 10 scale

EPSS, chance of exploitation in 30 days

0.2%

Higher than 8% of scored CVEs. A prediction, not evidence.

CISA remediation deadline

None

Not in the KEV catalog

Description

In the Linux kernel, the following vulnerability has been resolved: ALSA: bcd2000: Fix use-after-free of MIDI URBs on file close bcd2000_disconnect() calls snd_card_disconnect(), which only prevents new opens, and then frees the MIDI URBs. A rawmidi file that was already open can still be closed afterwards, and its close callback, bcd2000_midi_output_close(), calls usb_kill_urb() on midi_out_urb. The URB pointers are cleared on disconnect and their accesses are serialized with midi_lock, but bcd2000_midi_output_close() reads midi_out_urb without that lock. The check can therefore pass just before the pointer is cleared, and usb_kill_urb() then runs on the URB that has already been freed: BUG: KASAN: slab-use-after-free in usb_kill_urb+0x74/0x80 Read of size 8 at addr ffff8880078e7d40 usb_kill_urb bcd2000_midi_output_close close_substream rawmidi_release_priv snd_rawmidi_release Allocated by: usb_alloc_urb <- bcd2000_init_midi <- bcd2000_probe Freed by: usb_free_urb <- bcd2000_midi_free <- bcd2000_disconnect Take the lock in bcd2000_midi_output_close() and reference the URB with usb_get_urb() before releasing it. The URB then stays valid until usb_put_urb() after usb_kill_urb() has returned, even if a disconnect frees it in the meantime. usb_kill_urb() itself cannot run under midi_lock, as the completion handler takes the same lock.

Patching and mitigation

Patch status
Fix available (source: CVE record (Linux))
Fix documented (source date)
Mitigation
None documented
Vendor guidance
msrc.microsoft.com (opens in a new tab)

Affected products

VendorProductAffected versionsFixed inPer
LinuxLinuxfrom b47a22290d581277be70e8a597824a4985d39e83 before 791c259be56d05f90f7642df337f209c108003fa791c259be56d05f90f7642df337f209c108003faCVE Program
LinuxLinuxfrom b47a22290d581277be70e8a597824a4985d39e83 before 752eea15d0e67a468e484c1f166cdba694ba6de0752eea15d0e67a468e484c1f166cdba694ba6de0CVE Program
LinuxLinuxfrom b47a22290d581277be70e8a597824a4985d39e83 before a4c306eb3ba35a1e7201e25aef7e0537da609e72a4c306eb3ba35a1e7201e25aef7e0537da609e72CVE Program
LinuxLinuxfrom b47a22290d581277be70e8a597824a4985d39e83 before f6c7bb1f0799591a62be75b9bcf84245b4f208b7f6c7bb1f0799591a62be75b9bcf84245b4f208b7CVE Program
LinuxLinux3.16Not documentedCVE Program
Microsoftazl3 kernel 6.6.161.1-1 on Azure Linux 3.0Not documentedNot documentedMicrosoft MSRC
LinuxLinux (unaffected)from 6.12.118 up to and including 6.12.*Not documentedCVE Program
LinuxLinux (unaffected)from 6.18.64 up to and including 6.18.*Not documentedCVE Program
LinuxLinux (unaffected)from 7.3.5 up to and including 7.3.*Not documentedCVE Program
LinuxLinux (unaffected)7.4-rc2Not documentedCVE Program
LinuxLinux (unaffected)all versions before 3.16Not documentedCVE Program

Timeline

  1. Disclosure

    CVE record published by Linux

    Source: CVE Program (opens in a new tab)

  2. Patch

    Fix documented by CVE record (Linux)

    Source: CVE record (Linux) (opens in a new tab)

  3. Advisory

    Microsoft advisory published

    Source: Microsoft MSRC (opens in a new tab)

  4. Advisory change

    Microsoft advisory revised (2.0): Information published.

    Source: Microsoft MSRC (opens in a new tab)

Vendor guidance and references