CVE-2024-57804

What it actually does

Race condition in mpi3mr SAS driver corrupts persistent and current config pages for SAS IO unit and SAS Expander when multiple PHYs are disabled and enabled rapidly via the sysfs interface exposed by the SAS transport layer.

Why it matters to the business

Storage controllers using the affected driver may experience configuration corruption leading to loss of PHY state control, potential I/O failures, and degraded storage reliability on Linux systems; low exploit likelihood reduces immediate urgency despite long time since publication.

How an attack unfolds

An attacker with local access to sysfs rapidly toggles multiple PHY states in succession, triggering the race that overwrites shared config page memory and leaves the SAS setup in a corrupted state.

How to fix it

Apply the upstream fix that allocates separate memory for each config request; upgrade the Linux kernel to a version containing the resolution for CVE-2024-57804.

How to confirm the fix worked

Confirm kernel source contains the separate-memory allocation change for config pages; verify sysfs PHY toggle operations no longer share memory buffers; test rapid PHY state changes under load.

Typical attack path

1. Obtain local access to a system running the vulnerable mpi3mr driver
2. Locate the sysfs entries for SAS PHY enable/disable controls
3. Issue rapid successive disable/enable operations across multiple PHYs
4. Trigger memory reuse that corrupts SAS IO unit and expander config pages
5. Observe resulting storage configuration errors or I/O disruptions

How to detect it

Review system logs for mpi3mr or SAS config page errors following rapid PHY changes; examine kernel oops or warning messages referencing corrupted SAS IO unit pages.

What your security team should do

• Prioritize kernel updates on systems exposing mpi3mr SAS controllers
• Monitor EPSS trend for any increase indicating rising exploit interest
• Restrict unprivileged write access to relevant sysfs SAS PHY controls where possible