CVE-2024-38600: ALSA: Fix deadlocks with kctl removals at disconnection
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.
Security readout for executives and security teams
Plain-English summary
CVE-2024-38600 is a Linux kernel ALSA flaw that can deadlock sound-card control handling during device disconnection, especially when the device is suspended. The main business impact is availability: affected systems may hang in this subsystem and require recovery. No source in the bundle shows active exploitation.
Executive priority
Treat this as a routine-to-priority kernel availability fix, not an emergency internet-facing threat based on the provided evidence. Patch through normal kernel maintenance, with higher priority for workstations, kiosks, appliances, or systems dependent on stable audio hardware behavior.
Technical view
The issue is in ALSA snd_card_disconnect(). After card->shutdown is set, disconnect callbacks may remove kctl elements while another thread waits in snd_power_ref_and_wait() under card->controls_rwsem. Because sleepers were not woken before callbacks, snd_ctl_remove*() could block on the same lock. The fix wakes all waiters earlier.
Likely exposure
Linux systems using affected kernel versions and ALSA sound-card drivers are the relevant exposure. Practical risk appears highest where sound devices can disconnect while suspended and controls are accessed concurrently. Distribution backports may change exposure, so inventory must use vendor kernel advisory data.
Exploitation context
The provided sources describe a deadlock condition, not a public exploit or active exploitation. CISA KEV status is false in the bundle. The evidence supports availability risk under specific timing and device-state conditions, not remote code execution or privilege escalation.
Researcher notes
Evidence is limited to the CVE record and Linux stable commits. The root cause is lock ordering and wake-up timing around controls_rwsem, power_ref_sleep waiters, kctl removal, and disconnect callbacks. No CVSS, CWE, exploit proof, or distribution-specific fixed package list is provided.
Mitigation direction
Identify Linux kernel versions and distribution backport status across endpoints and servers.
Prioritize kernel updates that include the referenced ALSA stable fixes.
Check vendor or distribution advisories for packaged fixed kernel builds.
Reduce exposure to untrusted removable sound hardware where operationally feasible.
Plan reboots required for kernel remediation during maintenance windows.
Validation and detection
Confirm running kernel versions against vendor advisories and stable fix references.
Review package changelogs for CVE-2024-38600 or the ALSA kctl disconnect fix.
Check whether systems use ALSA sound-card drivers or removable audio devices.
Monitor logs for sound-card disconnect issues or kernel task hang symptoms.
Validate patched kernels after reboot with standard fleet compliance checks.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cve · low confidence lookup
CVE-2024-38600 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.