GHSA-FJCX-325H-XFM2
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: us122l: Fix NULL dereference at hwdep open and release
usb_stream_hwdep_open() and usb_stream_hwdep_release() pass the result of usb_ifnum_to_if() straight to usb_autopm_get_interface() and usb_autopm_put_interface(), without checking it for NULL.
usb_ifnum_to_if() returns NULL once the device is gone, since usb_disable_device() clears udev->actconfig on disconnect. The hwdep file can outlive the disconnect: the card is released with snd_card_free_when_closed(), so a process that keeps the character device open reaches the driver's release callback after the USB configuration has been dropped, and interface_to_usbdev() then dereferences the NULL interface at offsetof(struct device, parent). The open callback has the same problem when it races with the disconnect.
Check both lookups and fail the open with -ENODEV; in release, skip the runtime PM put when the interface is already gone and still run the rest of the per-file cleanup. Move the us122l->first bookkeeping after the checks so that a failed open no longer leaves a stale file pointer behind.
{
"affected": [],
"aliases": [
"CVE-2026-99315"
],
"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: us122l: Fix NULL dereference at hwdep open and release\n\nusb_stream_hwdep_open() and usb_stream_hwdep_release() pass the result of\nusb_ifnum_to_if() straight to usb_autopm_get_interface() and\nusb_autopm_put_interface(), without checking it for NULL.\n\nusb_ifnum_to_if() returns NULL once the device is gone, since\nusb_disable_device() clears udev-\u003eactconfig on disconnect. The hwdep file\ncan outlive the disconnect: the card is released with\nsnd_card_free_when_closed(), so a process that keeps the character device\nopen reaches the driver\u0027s release callback after the USB configuration has\nbeen dropped, and interface_to_usbdev() then dereferences the NULL\ninterface at offsetof(struct device, parent). The open callback has the\nsame problem when it races with the disconnect.\n\nCheck both lookups and fail the open with -ENODEV; in release, skip the\nruntime PM put when the interface is already gone and still run the rest\nof the per-file cleanup. Move the us122l-\u003efirst bookkeeping after the\nchecks so that a failed open no longer leaves a stale file pointer behind.",
"id": "GHSA-fjcx-325h-xfm2",
"modified": "2026-11-18T09:30:31Z",
"published": "2026-11-18T09:30:31Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-99315"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/3be1ac0b73e9bf73eec0000197d0177ebeb3cc79"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/57dc5db514ab188a24cb300bda70a1ead3c9e479"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/820e0050866942b5498488496462d12c6ce1c7a9"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/b21aa212c9ba4536e66d65783cc883951c95ba01"
}
],
"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.