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.