CVE-2026-99318

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

Published Nov 18, 2026 CVSS n/a EPSS n/a KEV · Not listed
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.

Analysis

AI-generated

Technical impact

A race condition in the ALSA bcd2000 driver causes a use‑after‑free of a USB URB when a rawmidi file that has already been opened is closed after the device has been disconnected. The driver frees the URB during disconnect, but a close callback may still reference the freed memory and call usb_kill_urb, resulting in kernel memory corruption and a panic. This weakness is a classic use‑after‑free scenario (CWE‑416). While the kernel crash does not provide direct remote code execution, it can be used for denial of service, and in theory could be leveraged for local privilege escalation if the attacker can influence the corrupted memory.

Affected Systems

The flaw affects all Linux kernels that include the unpatched bcd2000 ALSA driver. Any distribution shipping a kernel prior to the commit that adds the proper locking and reference counting is vulnerable. No specific version numbers are listed, so all kernels containing the buggy driver are at risk.

Risk and Exploitability

The CVSS score is not provided and the EPSS score is unavailable, so the likelihood of exploitation is unknown. The attack vector is local: an attacker must have access to a bcd2000 USB device, be able to open a rawmidi file, disconnect the device, and then close the file, triggering the race. No public exploits are documented, but the impact is a kernel panic that could serve as a denial‑of‑service vector, with potential privilege‑escalation risk if the kernel memory corruption can be exploited further.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade your Linux kernel to a version that contains the bcd2000 driver fix.
  • Reboot the system so the updated kernel and driver are loaded.
  • If an update cannot be applied immediately, disable the bcd2000 driver by blacklisting the module or removing any connected bcd2000 hardware to prevent the race condition.

Generated by OpenCVE AI on November 18, 2026 at 23:13 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
Weaknesses CWE-416
Type Values Removed Values Added
First Time appeared Linux linux
Vendors & Products Linux linux
Type Values Removed Values Added
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.
Title ALSA: bcd2000: Fix use-after-free of MIDI URBs on file close
First Time appeared Linux
Linux linux Kernel
CPEs cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
Vendors & Products Linux
Linux linux Kernel
References
Weaknesses

Sources

Status
PUBLISHED
Assigner
Linux
Published
Updated
Nov 18, 2026, 8:42 AM
Reserved
Sep 25, 2026, 10:25 AM
Status
Received
Published
Nov 18, 2026, 9:17 AM
Modified
Nov 18, 2026, 9:17 AM