CPU soft lockup via unyielding interrupt loop
Published Dec 27, 2024 · Updated May 11, 2026
Denial of service in the hisi_sas driver in affected Linux kernels allows local users to trigger a CPU soft lockup through sustained SAS I/O. On non-preemptible kernels, irq_wait_for_interrupt() repeatedly returns zero during interrupt storms, monopolizing the shared interrupt CPU and starving the watchdog thread. Reachability requires the hisi_sas v3 driver, an expander connected to 12 high-performance SAS SSDs, heavy interrupt load, and low-privileged local access; the bounded consequence is a CPU soft lockup and service interruption.
Summary
What happened
Denial of service in the hisi_sas driver in affected Linux kernels allows local users to trigger a CPU soft lockup through sustained SAS I/O. On non-preemptible kernels, irq_wait_for_interrupt() repeatedly returns zero during interrupt storms, monopolizing the shared interrupt CPU and starving the watchdog thread. Reachability requires the hisi_sas v3 driver, an expander connected to 12 high-performance SAS SSDs, heavy interrupt load, and low-privileged local access; the bounded consequence is a CPU soft lockup and service interruption.
The record
- CVE
- CVE-2024-56589
- Published
- Dec 27, 2024
- Updated
- May 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- T1499.001
- 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=4.5
- Affected versionversion=47caad1577cd7a39e2048c5e4edbce4b863dc12b <2174bbc235f79fce88ea71fd08cf836568fcad5f
- Affected versionversion=47caad1577cd7a39e2048c5e4edbce4b863dc12b <2233c4a0b948211743659b24c13d6bd059fa75fc
- Affected versionversion=47caad1577cd7a39e2048c5e4edbce4b863dc12b <2991a023896b79e6753813ed88fbc98979713c73
- Affected versionversion=47caad1577cd7a39e2048c5e4edbce4b863dc12b <3dd2c5cb2c698a02a4ed2ea0acb7c9909374a8bf
- Affected versionversion=47caad1577cd7a39e2048c5e4edbce4b863dc12b <50ddf4b0e1a4cb5e9ca0aac3d0a73202b903c87f
- Affected versionversion=47caad1577cd7a39e2048c5e4edbce4b863dc12b <601f8001373fc3fbad498f9be427254908b7fcce
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