Local soft lockup via synchronous USB teardown
Published Dec 27, 2024 · Updated May 11, 2026
Improper locking in affected Linux kernel branches allows local users to cause a soft lockup by disconnecting an open usx2y USB device. The snd_usx2y_disconnect callback calls snd_card_free, which waits for every open sound-card file descriptor instead of deferring resource release. Reachability requires local access, a connected usx2y USB audio device, an open descriptor, and device disconnection; the resulting stall blocks upper-layer USB ioctls.
Summary
What happened
Improper locking in affected Linux kernel branches allows local users to cause a soft lockup by disconnecting an open usx2y USB device. The snd_usx2y_disconnect callback calls snd_card_free, which waits for every open sound-card file descriptor instead of deferring resource release. Reachability requires local access, a connected usx2y USB audio device, an open descriptor, and device disconnection; the resulting stall blocks upper-layer USB ioctls.
The record
- CVE
- CVE-2024-56533
- Published
- Dec 27, 2024
- Updated
- May 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-667, T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Dec 27, 2024CVE publishedPublication date reported by the CVE source.
- May 11, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=230cd5e24853ed4dd960461989b8ed0986d37a99 <24fe9f7ca83ec9acf765339054951f5cd9ae5c5d
- Affected versionversion=230cd5e24853ed4dd960461989b8ed0986d37a99 <7bd8838c0ea886679a32834fdcacab296d072fbe
- Affected versionversion=230cd5e24853ed4dd960461989b8ed0986d37a99 <befcca1777525e37c659b4129d8ac7463b07ef67
- Affected versionversion=230cd5e24853ed4dd960461989b8ed0986d37a99 <dafb28f02be407e07a6f679e922a626592b481b0
- Affected versionversion=230cd5e24853ed4dd960461989b8ed0986d37a99 <e07605d855c4104d981653146a330ea48f6266ed
- Affected versionversion=230cd5e24853ed4dd960461989b8ed0986d37a99 <e869642a77a9b3b98b0ab2c8fec7af4385140909
- Affected versionversion=230cd5e24853ed4dd960461989b8ed0986d37a99 <ffbfc6c4330fc233698529656798bee44fea96f5
- Affected versionversion=2.6.13
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
- syzbot snd_card_free task-hang reproducerproof of concept · validated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo