Local hard lockup via serialized SCSI recovery scans
Published Mar 6, 2024 · Updated May 11, 2026
Denial of service in the SCSI core of affected Linux kernel releases allows local users to cause a hard lockup during error recovery. The scsi_eh_wakeup() path calls scsi_host_busy() while holding the host lock, repeatedly scanning every tagged request and serializing concurrent wakeups. A practical lockup requires large hardware-queue and queue-depth values with all requests in flight; the reported case used mpi3mr with 128 queues at depth 8169.
Summary
What happened
Denial of service in the SCSI core of affected Linux kernel releases allows local users to cause a hard lockup during error recovery. The scsi_eh_wakeup() path calls scsi_host_busy() while holding the host lock, repeatedly scanning every tagged request and serializing concurrent wakeups. A practical lockup requires large hardware-queue and queue-depth values with all requests in flight; the reported case used mpi3mr with 128 queues at depth 8169.
The record
- CVE
- CVE-2024-26627
- Published
- Mar 6, 2024
- Updated
- May 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Mar 6, 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=5.5
- Affected versionversion=6eb045e092efefafc6687409a6fa6d1dabf0fb69 <07e3ca0f17f579491b5f54e9ed05173d6c1d6fcb
- Affected versionversion=6eb045e092efefafc6687409a6fa6d1dabf0fb69 <4373534a9850627a2695317944898eb1283a2db0
- Affected versionversion=6eb045e092efefafc6687409a6fa6d1dabf0fb69 <65ead8468c21c2676d4d06f50b46beffdea69df1
- Affected versionversion=6eb045e092efefafc6687409a6fa6d1dabf0fb69 <d37c1c81419fdef66ebd0747cf76fb8b7d979059
- Affected versionversion=6eb045e092efefafc6687409a6fa6d1dabf0fb69 <db6338f45971b4285ea368432a84033690eaf53c
- Affected versionversion=6eb045e092efefafc6687409a6fa6d1dabf0fb69 <f5944853f7a961fedc1227dc8f60393f8936d37c
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