SCSI operation hang via inverted lock order
Published Jan 11, 2025 · Updated May 23, 2026
Improper locking in the Linux kernel megaraid_sas driver allows local users to interrupt SCSI controller reset and scan operations. The driver acquires reset_mutex and scan_mutex in opposite orders across reset and host-scan paths, creating a circular wait. Triggering the condition requires local access and concurrent execution of the affected SCSI paths; no data disclosure or modification is reported.
Summary
What happened
Improper locking in the Linux kernel megaraid_sas driver allows local users to interrupt SCSI controller reset and scan operations. The driver acquires reset_mutex and scan_mutex in opposite orders across reset and host-scan paths, creating a circular wait. Triggering the condition requires local access and concurrent execution of the affected SCSI paths; no data disclosure or modification is reported.
The record
- CVE
- CVE-2024-57807
- Published
- Jan 11, 2025
- Updated
- May 23, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-667, T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jan 11, 2025CVE publishedPublication date reported by the CVE source.
- May 23, 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=2262bb7ee19e2d0056ffae84cd1803bd330d06af
- Affected versionversion=422fb12054f42c4c82e3959811afd01bc080821a <f36d024bd15ed356a80dda3ddc46d0a62aa55815
- Affected versionversion=5.10.52 <5.10.233
- Affected versionversion=5.12.19 <5.13
- Affected versionversion=5.13.4 <5.14
- Affected versionversion=5.14
- Affected versionversion=5.4.134 <5.4.289
- Affected versionversion=5f4f65212e42feaee32533448f1c1defdaa6befa
- Affected versionversion=ae6874ba4b43c5a00065f48599811a09d33b873d <3c654998a3e8167a58b6c6fede545fe400a4b554
- Affected versionversion=ae6874ba4b43c5a00065f48599811a09d33b873d <466ca39dbf5d0ba71c16b15c27478a9c7d4022a8
- Affected versionversion=ae6874ba4b43c5a00065f48599811a09d33b873d <50740f4dc78b41dec7c8e39772619d5ba841ddd7
- Affected versionversion=ae6874ba4b43c5a00065f48599811a09d33b873d <edadc693bfcc0f1ea08b8fa041c9361fd042410d
- Affected versionversion=ae6874ba4b43c5a00065f48599811a09d33b873d <f50783148ec98a1d38b87422e2ceaf2380b7b606
- Affected versionversion=e8c75b5d88f255ac5dcc4a90ae0c300f0b171fe7 <78afb9bfad00c4aa58a424111d7edbcab9452f2b
What conditions does exploitation require?
What is affected?
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