CVE-2024-38600: Linux kernel · ALSA: Fix deadlocks with kctl removals at disconnection
Affects Linux kernelSource GCVE Database
Not known to be exploited · CVSS 5.5 Medium · fixed in 5.15.0-1067.73~20.04.1 : update Linux kernel when convenient.
Data as of 12 Nov 2026, 19:04 UTC
- Patch
- Available – fixed in 5.15.0-1067.73~20.04.1, 5.15.0-1070.79~20.04.1, 5.15.0-1066.74~20.04.1 +51
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:HExploitation evidence
Disclosed: evidence found.
CVE published 19 Jun 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 12 Nov 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Patches and advisories
- ubuntu.com/security/notices/USN-6949-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-6950-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-6951-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-6952-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-6953-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-6955-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-6956-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-6957-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-6950-2 (opens in a new tab)
- ubuntu.com/security/notices/USN-6950-3 (opens in a new tab)
- ubuntu.com/security/notices/USN-6949-2 (opens in a new tab)
- ubuntu.com/security/notices/USN-6952-2 (opens in a new tab)
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Ubuntu 24.04 LTSlinuxpkg:deb/ubuntu/linux?arch=source&distro=nobleOther threats | Affected
| Fixed in
|
Ubuntu 24.04 LTSlinux-awspkg:deb/ubuntu/linux-aws?arch=source&distro=nobleOther threats | Affected
| Fixed in
|
Ubuntu 24.04 LTSlinux-azurepkg:deb/ubuntu/linux-azure?arch=source&distro=nobleOther threats | Affected
| Fixed in
|
Ubuntu 24.04 LTSlinux-gcppkg:deb/ubuntu/linux-gcp?arch=source&distro=nobleOther threats | Affected
| Fixed in
|
Ubuntu 24.04 LTSlinux-gkepkg:deb/ubuntu/linux-gke?arch=source&distro=nobleOther threats | Affected
| Fixed in
|
Ubuntu 24.04 LTSlinux-ibmpkg:deb/ubuntu/linux-ibm?arch=source&distro=nobleOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
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.
References
- ubuntu.com/security/CVE-2024-38600 (opens in a new tab)
- cve.org/CVERecord?id=CVE-2024-38600 (opens in a new tab)
- git.kernel.org/linus/87988a534d8e12f2e6fc01fe63e6c1925dc5307c (opens in a new tab)
- git.kernel.org/stable/c/ff80185e7b7b547a0911fcfc8aefc61c3e8304d7 (opens in a new tab)
- git.kernel.org/stable/c/c2fb439f4f1425a961d20bec818fed2c2d9ef70a (opens in a new tab)
- git.kernel.org/stable/c/2f103287ef7960854808930499d1181bd0145d68 (opens in a new tab)
- git.kernel.org/stable/c/88ce3fe255d58a93624b467af036dc3519f309c7 (opens in a new tab)
- git.kernel.org/stable/c/6b55e879e7bd023a03888fc6c8339edf82f576f4 (opens in a new tab)
- git.kernel.org/stable/c/87988a534d8e12f2e6fc01fe63e6c1925dc5307c (opens in a new tab)
- ubuntu.com/security/notices/USN-6949-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-6950-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-6951-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-6952-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-6953-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-6955-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-6956-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-6957-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-6950-2 (opens in a new tab)
- ubuntu.com/security/notices/USN-6950-3 (opens in a new tab)
- ubuntu.com/security/notices/USN-6949-2 (opens in a new tab)