CVE-2026-99317
ALSA: hwdep: Serialize DSP load requests
What happened?
In the Linux kernel, the following vulnerability has been resolved:
ALSA: hwdep: Serialize DSP load requests
The check of the loaded DSP indices and the call of the driver's dsp_load callback in snd_hwdep_dsp_load() are not serialized. A hwdep file descriptor can be shared among threads, or inherited across fork, so two SNDRV_HWDEP_IOCTL_DSP_LOAD requests for the same index can both observe the index as unloaded and enter the driver's callback concurrently, even though the device itself is opened exclusively.
This breaks the assumption behind hw->dsp_loaded that a firmware index is loaded only once. For example, snd-usb-usx2y hits WARN_ON(usx2y->as04.buffer) in usx2y_async_seq04_init() and may allocate the US-428 sequence URBs twice.
Serialize the check, the callback invocation and the bookkeeping with a per-hwdep mutex, so that the second request returns -EBUSY.
Affected software and versions
| Software | Version information | Fixed version |
|---|---|---|
| LinuxLinux | affected: 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 to < 200bda52a9fd604e13c57d3a548639c13bdfb19c; affected: 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 to < 3634a1beb0395f02807d41a2edf4288732d3f90e; affected: 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 to < 1b94ca29b1edbbdb357c2c8a9163d1d1755e4ad2; affected: 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 to < aee83c204f80d56b4d55f53acdb8594308ddcd4a | See vendor advisory |
| LinuxLinux | affected: 2.6.12; unaffected: 0 to < 2.6.12; unaffected: 6.12.118 to ≤ 6.12.*; unaffected: 6.18.64 to ≤ 6.18.*; unaffected: 7.3.5 to ≤ 7.3.*; unaffected: 7.4-rc2 to ≤ * | See vendor advisory |
Version information comes from the source record and can include unaffected products and exceptions. Distribution packages may contain backported fixes: an older upstream version alone does not prove a server is affected.
Is it being exploited?
This CVE was not listed in the CISA catalogue at our last retrieval. This does not establish that exploitation is absent.
How to respond
- Confirm the product, installed package version, and any configuration requirements in the vendor advisory.
- Follow the vendor’s remediation or workaround guidance in the references below. Structured fixed-version data is unavailable here; the publisher’s description may include a fix or workaround.
- Restart affected services if required, then verify the running version. Known exploitation may warrant investigation as well as patching.
Sources and remediation references
- https://www.cve.org/CVERecord?id=CVE-2026-99317
- https://git.kernel.org/stable/c/200bda52a9fd604e13c57d3a548639c13bdfb19c
- https://git.kernel.org/stable/c/3634a1beb0395f02807d41a2edf4288732d3f90e
- https://git.kernel.org/stable/c/1b94ca29b1edbbdb357c2c8a9163d1d1755e4ad2
- https://git.kernel.org/stable/c/aee83c204f80d56b4d55f53acdb8594308ddcd4a