Linux kernel megaraid_sas driver potential deadlock
CVE-2024-57807 is a potential deadlock in the Linux kernel SCSI MegaRAID SAS driver (megaraid_sas). A lock-order inversion can occur between instance->reset_mutex and the SCSI host scan_mutex: one execution path can hold reset_mutex while waiting for scan_mutex, while another holds scan_mutex while waiting for reset_mutex. The upstream fix temporarily releases reset_mutex before acquiring scan_mutex, eliminating the circular locking dependency.
What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
Concurrent affected driver operations can deadlock kernel execution paths associated with MegaRAID SAS controller reset and SCSI-host scanning. This can stall I/O or related system operations, resulting in a denial of service for the affected host or storage subsystem.
If you can’t patch tonight, do this now.
No separate temporary workaround is specified. Until the fixed kernel can be deployed, reduce exposure by avoiding or tightly controlling concurrent MegaRAID controller reset and SCSI scan activity where operationally feasible.
Patch, then assume compromise.
Install a vendor kernel update containing the upstream megaraid_sas locking fix and reboot into the updated kernel. For Red Hat Enterprise Linux 8, fixed builds include kernel 4.18.0-553.44.1.el8_10 and kernel-rt 4.18.0-553.44.1.rt7.385.el8_10. Apply the applicable vendor update for other supported Linux distributions.
No public exploits tracked yet. Mallory keeps watching.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
5 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.