CVE-2024-38600ALSA: Fix deadlocks with kctl removals at disconnection
- 5.5MediumCVSS base score
- 0.19%Exploitation in 30 daysEPSS · top 91% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
Description
In the Linux kernel, the following vulnerability has been resolved: ALSA: Fix deadlocks with kctl removals at disconnection In snd_card_disconnect(), we set card->shutdown flag at the beginning, call callbacks and do sync for card->power_ref_sleep waiters at the end. The callback may delete a kctl element, and this can lead to a deadlock when the device was in the suspended state. Namely: * A process waits for the power up at snd_power_ref_and_wait() in snd_ctl_info() or read/write() inside card->controls_rwsem. * The system gets disconnected meanwhile, and the driver tries to delete a kctl via snd_ctl_remove*(); it tries to take card->controls_rwsem again, but this is already locked by the above. Since the sleeper isn't woken up, this deadlocks. An easy fix is to wake up sleepers before processing the driver disconnect callbacks but right after setting the card->shutdown flag. Then all sleepers will abort immediately, and the code flows again. So, basically this patch moves the wait_event() call at the right timing. While we're at it, just to be sure, call wait_event_all() instead of wait_event(), although we don't use exclusive events on this queue for now.
Timeline
ID reserved
By Linux
- 1 day later
· 1 day later
Published
- 23 months later
· 23 months later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| NVDNVD · Modified | 3.1 | Medium5.5 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
- EPSS (exploitation in 30 days)
- 0.19% · top 91% of all CVEs (13 Nov 2026)
- CISA SSVC
- Exploitation: none · Automatable: no · Technical impact: partial
The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.
Affected products
- affected e94fdbd7b25d87e64688bb109e2c550217a4c879 – < ff80185e7b7b547a0911fcfc8aefc61c3e8304d7
- affected e94fdbd7b25d87e64688bb109e2c550217a4c879 – < c2fb439f4f1425a961d20bec818fed2c2d9ef70a
- affected e94fdbd7b25d87e64688bb109e2c550217a4c879 – < 2f103287ef7960854808930499d1181bd0145d68
- affected e94fdbd7b25d87e64688bb109e2c550217a4c879 – < 88ce3fe255d58a93624b467af036dc3519f309c7
- affected e94fdbd7b25d87e64688bb109e2c550217a4c879 – < 6b55e879e7bd023a03888fc6c8339edf82f576f4
- affected e94fdbd7b25d87e64688bb109e2c550217a4c879 – < 87988a534d8e12f2e6fc01fe63e6c1925dc5307c
- affected 5.14
- unaffected < 5.14
- unaffected 5.15.161 – ≤ 5.15.*
- unaffected 6.1.93 – ≤ 6.1.*
- unaffected 6.6.33 – ≤ 6.6.*
- unaffected 6.8.12 – ≤ 6.8.*
- unaffected 6.9.3 – ≤ 6.9.*
- unaffected 6.10 – ≤ *
References
References6
- https://git.kernel.org/stable/c/ff80185e7b7b547a0911fcfc8aefc61c3e8304d7 (opens in a new tab)x_transferred
- https://git.kernel.org/stable/c/c2fb439f4f1425a961d20bec818fed2c2d9ef70a (opens in a new tab)x_transferred
- https://git.kernel.org/stable/c/2f103287ef7960854808930499d1181bd0145d68 (opens in a new tab)x_transferred
- https://git.kernel.org/stable/c/88ce3fe255d58a93624b467af036dc3519f309c7 (opens in a new tab)x_transferred
- https://git.kernel.org/stable/c/6b55e879e7bd023a03888fc6c8339edf82f576f4 (opens in a new tab)x_transferred
- https://git.kernel.org/stable/c/87988a534d8e12f2e6fc01fe63e6c1925dc5307c (opens in a new tab)x_transferred
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2024-37463 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2024-38600)Record last updated .