CVE-2024-57804

In the Linux kernel, the following vulnerability has been resolved:

scsi: mpi3mr: Fix corrupt config pages PHY state is switched in sysfs

The driver, through the SAS transport, exposes a sysfs interface to enable/disable PHYs in a controller/expander setup. When multiple PHYs are disabled and enabled in rapid succession, the persistent and current config pages related to SAS IO unit/SAS Expander pages could get corrupted.

Use separate memory for each config request.

A flaw was found in the Linux kernel's mpi3mr SCSI driver, which exposes a sysfs interface through the SAS transport layer for enabling and disabling PHYs on a controller or expander. When multiple PHYs are disabled and enabled in rapid succession, the persistent and current configuration pages related to the SAS IO unit and SAS Expander pages can become corrupted, which may disrupt storage connectivity and system availability on systems using mpi3mr-managed controllers. Red Hat rates this issue as LOW severity because exploitation requires local privileged access and deliberate interaction with the sysfs PHY interface, and the impact is limited to availability (Red Hat CVSS 4.4, AV:L/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H); this differs from the higher CVE.org score of 7.3, which also assumes confidentiality and integrity impact that is not established by the flaw's evidence. The kernel and kernel-rt packages in Red Hat Enterprise Linux 9 are affected and the fix is deferred in line with the LOW severity rating; the residual risk is that a local privileged user could corrupt the SAS IO unit and SAS Expander configuration pages through rapid PHY state changes via sysfs, affecting availability of mpi3mr-controlled storage. Red Hat Enterprise Linux 6 and 7 are not affected, and the Red Hat Enterprise Linux 8 update streams are out of support. The upstream fix uses separate memory for each configuration request.

The CVSS score(s) listed for this vulnerability do not reflect the associated product's status, and are included for informational purposes to better understand the severity of this vulnerability.

Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability.