System deadlock via interrupt-unsafe SCTP locking
Published Jan 17, 2024 · Updated Jul 21, 2026
Deadlock in the Linux Kernel before 6.5-rc1 allows local users to hang or crash the system through the SCTP socket accept path. sctp_auto_asconf_init acquires addr_wq_lock without disabling bottom halves, allowing the SCTP timer handler to interrupt it and reacquire the same lock. Exploitation requires local low-privileged guest access and enabled SCTP automatic address configuration, and it affects availability only.
Summary
What happened
Deadlock in the Linux Kernel before 6.5-rc1 allows local users to hang or crash the system through the SCTP socket accept path. sctp_auto_asconf_init acquires addr_wq_lock without disabling bottom halves, allowing the SCTP timer handler to interrupt it and reacquire the same lock. Exploitation requires local low-privileged guest access and enabled SCTP automatic address configuration, and it affects availability only.
The record
- CVE
- CVE-2024-0639
- Published
- Jan 17, 2024
- Updated
- Jul 21, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- CWE-833, CAPEC-25, T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jan 17, 2024CVE publishedPublication date reported by the CVE source.
- Jul 21, 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=0 <6.5-rc1
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.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
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