Security readout for executives and security teams
Plain-English summary
A Linux storage-controller driver can corrupt active and saved SAS configuration when several hardware links are disabled and re-enabled quickly through sysfs. Corruption could disrupt storage connectivity or alter controller configuration. Triggering requires local, privileged access to the relevant management interface; ordinary remote traffic is not identified as an attack path.
Executive priority
Prioritize storage servers that use mpi3mr and permit automated or delegated hardware-link management. Patch them during an expedited, storage-aware maintenance window because configuration corruption could affect availability and persistence. Systems without the driver or relevant controller hardware are unlikely to be exposed and can remain on normal verification schedules.
Technical view
The mpi3mr SCSI driver reused memory across SAS configuration requests. Rapid, overlapping PHY state changes could corrupt current and persistent SAS IO Unit or SAS Expander configuration pages. The cited kernel fixes allocate separate memory for each request. The supplied CVSS 3.1 score is 7.3, reflecting local access, low complexity, low privileges, and potentially high integrity and availability impact.
Likely exposure
Exposure is limited to Linux systems using the mpi3mr driver with supported controllers or expanders and accessible PHY-control sysfs entries. Local users, management software, or automation able to change those entries create the relevant trigger path. The bundle identifies affected Linux releases including 6.1, 6.12.8, and 6.13, but its version data is ambiguous; verify distribution-specific status.
Exploitation context
The supplied record is not in CISA KEV, and no source in the bundle reports active exploitation or a public exploit. The condition requires rapid local PHY state changes through sysfs. Accidental triggering by privileged storage-management automation may therefore be as operationally relevant as deliberate abuse.
Researcher notes
The strongest evidence concerns a concurrency-related memory-sharing flaw in configuration handling, not remote code execution. The precise affected-version boundaries are unclear in the supplied normalized data. Researchers should compare distribution patches with the two upstream stable commits and assess sysfs authorization, concurrent request handling, and configuration integrity without reproducing corruption on production storage.
Mitigation direction
- Install a vendor-supported kernel containing the cited mpi3mr fixes.
- Confirm distribution backport status rather than relying only on the upstream kernel version.
- Restrict sysfs PHY-control access to trusted administrators and management services.
- Avoid rapid or concurrent PHY enable-disable operations until patched.
- Review vendor guidance before changing production storage-controller behavior.
Validation and detection
- Inventory hosts loading mpi3mr and identify attached controllers or SAS expanders.
- Record running kernel and distribution package versions on exposed hosts.
- Verify the kernel package includes either cited fix or an equivalent vendor backport.
- Review permissions and automation accessing PHY-control sysfs entries.
- Check storage and kernel logs for PHY resets, controller errors, or configuration anomalies.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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.
CVE-2024-57804 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 7.3 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:H/A:H
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.
CVSS vector scores
1 official scoreWe 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.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:H/A:H1.85.5LinuxVulnerability scoring details
Base CVSS 3.1 score
7.3HighVector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:H/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
Source materials
- CVE List V5 sourceCVE List V5
- https://git.kernel.org/stable/c/869fdc6f0606060301aef648231e186c7c542f5aCVE reference, Linux
- https://git.kernel.org/stable/c/711201a8b8334a397440ac0b859df0054e174bc9CVE reference, Linux
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.