GHSA-5VMM-5WJ9-F8XG
Vulnerability from github – Published: 2026-11-18 09:30 – Updated: 2026-11-18 09:30In 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.
{
"affected": [],
"aliases": [
"CVE-2026-99318"
],
"database_specific": {
"cwe_ids": [],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-11-18T09:17:45Z",
"severity": null
},
"details": "In the Linux kernel, the following vulnerability has been resolved:\n\nALSA: bcd2000: Fix use-after-free of MIDI URBs on file close\n\nbcd2000_disconnect() calls snd_card_disconnect(), which only prevents\nnew opens, and then frees the MIDI URBs. A rawmidi file that was\nalready open can still be closed afterwards, and its close callback,\nbcd2000_midi_output_close(), calls usb_kill_urb() on midi_out_urb.\n\nThe URB pointers are cleared on disconnect and their accesses are\nserialized with midi_lock, but bcd2000_midi_output_close() reads\nmidi_out_urb without that lock. The check can therefore pass just\nbefore the pointer is cleared, and usb_kill_urb() then runs on the URB\nthat has already been freed:\n\n BUG: KASAN: slab-use-after-free in usb_kill_urb+0x74/0x80\n Read of size 8 at addr ffff8880078e7d40\n usb_kill_urb\n bcd2000_midi_output_close\n close_substream\n rawmidi_release_priv\n snd_rawmidi_release\n\n Allocated by: usb_alloc_urb \u003c- bcd2000_init_midi \u003c- bcd2000_probe\n Freed by: usb_free_urb \u003c- bcd2000_midi_free\n \u003c- bcd2000_disconnect\n\nTake the lock in bcd2000_midi_output_close() and reference the URB with\nusb_get_urb() before releasing it. The URB then stays valid until\nusb_put_urb() after usb_kill_urb() has returned, even if a disconnect\nfrees it in the meantime. usb_kill_urb() itself cannot run under\nmidi_lock, as the completion handler takes the same lock.",
"id": "GHSA-5vmm-5wj9-f8xg",
"modified": "2026-11-18T09:30:31Z",
"published": "2026-11-18T09:30:31Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-99318"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/752eea15d0e67a468e484c1f166cdba694ba6de0"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/791c259be56d05f90f7642df337f209c108003fa"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/a4c306eb3ba35a1e7201e25aef7e0537da609e72"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/f6c7bb1f0799591a62be75b9bcf84245b4f208b7"
}
],
"schema_version": "1.4.0",
"severity": []
}
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.