LiveActive security incident?Get immediate response
CVE Record

CVE-2024-57807: scsi: megaraid_sas: Fix for a potential deadlock

In the Linux kernel, the following vulnerability has been resolved: scsi: megaraid_sas: Fix for a potential deadlock This fixes a 'possible circular locking dependency detected' warning CPU0 CPU1 ---- ---- lock(&instance->reset_mutex); lock(&shost->scan_mutex); lock(&instance->reset_mutex); lock(&shost->scan_mutex); Fix this by temporarily releasing the reset_mutex.

MediumCVSS 5.5Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2024-57807 is a Linux kernel flaw in the megaraid_sas storage driver that can cause a deadlock. The practical impact is availability: affected systems may hang or become unable to complete storage-related work. The CVSS score is 5.5 because exploitation is local, requires low privileges, and does not affect confidentiality or integrity.

Executive priority

Treat this as a moderate operational resilience issue. Prioritize patching storage-heavy Linux servers and systems where downtime is costly. It does not appear to be a remote compromise issue based on the supplied sources.

Technical view

The vulnerability is a possible circular locking dependency between instance->reset_mutex and shost->scan_mutex in the Linux megaraid_sas SCSI driver. The kernel fix temporarily releases reset_mutex to avoid the deadlock. It is classified as CWE-667 and has CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H.

Likely exposure

Exposure is most likely on Linux systems running affected kernel versions where the megaraid_sas driver is present and used for storage controllers. Systems not using this driver are less likely to be exposed, but kernel packaging and backports should be checked through the operating system vendor.

Exploitation context

The bundle does not show CISA KEV listing or public active exploitation. The CVSS vector indicates local access with low privileges is required. The expected security outcome is denial of service or operational disruption, not data theft or code execution.

Researcher notes

Evidence supports a kernel locking bug with availability impact. The source bundle names stable kernel commits and Debian LTS advisories, but does not provide exploit reports, weaponized details, or universal package-level fixed versions across all distributions.

Mitigation direction

  • Update to a kernel or vendor package containing the referenced stable fixes.
  • For Debian LTS systems, review and apply the cited March 2025 advisories.
  • Check Linux distribution guidance for backported fixes before relying on version strings alone.
  • Prioritize servers where storage availability is business-critical.
  • If no vendor fix is available, seek vendor guidance for temporary risk reduction.

Validation and detection

  • Inventory Linux hosts running affected kernel branches.
  • Confirm whether the megaraid_sas driver is loaded or required.
  • Compare installed kernel packages against vendor advisories and fixed builds.
  • Review kernel changelogs for the megaraid_sas deadlock fix.
  • Test patched systems for storage-controller reset and scan stability.
Prepared
Confidence
high
Sources
11

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-667: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2024-57807 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
5.5 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
3Timeline events
2ADP providers
10Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: partial

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
5.5CVSS 3.1MediumCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H1.83.6CISA-ADP

Vulnerability scoring details

Base CVSS 3.1 score

5.5Medium
CVSS 3.1 vector shape for CVE-2024-57807Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
cvssV3_1other:ssvc
CVECVE Program Container
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxe8c75b5d88f255ac5dcc4a90ae0c300f0b171fe7, 422fb12054f42c4c82e3959811afd01bc080821a, ae6874ba4b43c5a00065f48599811a09d33b873d, ae6874ba4b43c5a00065f48599811a09d33b873d, ae6874ba4b43c5a00065f48599811a09d33b873d, ae6874ba4b43c5a00065f48599811a09d33b873d, ae6874ba4b43c5a00065f48599811a09d33b873d, 5f4f65212e42feaee32533448f1c1defdaa6befa, 2262bb7ee19e2d0056ffae84cd1803bd330d06af, 5.4.134, 5.10.52, 5.12.19, 5.13.4unaffected
LinuxLinux5.14, 0, 5.4.289, 5.10.233, 5.15.176, 6.1.123, 6.6.69, 6.12.8, 6.13affected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-667 · source CWE mapping

Improper Locking

Improper Locking represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.