CVE-2024-57804

Description

From CVE.org

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.

Statement

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.

Mitigation

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.

Common Vulnerability Scoring System (CVSS) Score Details

Info alert:Important note

CVSS scores for open source components depend on vendor-specific factors (e.g. version or build chain). Therefore, Red Hat's score and impact rating can be different from NVD and other vendors. Red Hat remains the authoritative CVE Naming Authority (CNA) source for its products and services (see Red Hat classifications).

The following CVSS metrics and score provided are preliminary and subject to review.

CVSS v3 Score Breakdown

Red HatNVDcve.org
Base Score4.45.57.3
Attack VectorLocalLocalLocal
Attack ComplexityLowLowLow
Privileges RequiredHighLowLow
User InteractionNoneNoneNone
ScopeUnchangedUnchangedUnchanged
ConfidentialityNoneNoneLow
Integrity ImpactNoneNoneHigh
Availability ImpactHighHighHigh

Vector

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

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

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

Understanding the Weakness (CWE)

Other

Technical Impact: Varies by Context

The resource might be left in an unexpected state when it is accessed or used.

Confidentiality

Technical Impact: Read Memory; Read Application Data

When reusing a resource such as memory or a program variable, the original contents of that resource may not be cleared before it is sent to an untrusted party.

Access Control

Technical Impact: Bypass Protection Mechanism

If security-critical decisions rely on a variable having a "0" or equivalent value, and the programming language performs this initialization on behalf of the programmer, then a bypass of security may occur.

Availability

Technical Impact: DoS: Crash, Exit, or Restart

The uninitialized data may contain values that cause program flow to change in ways that the programmer did not intend. For example, if an uninitialized variable is used as an array index in C, then its previous contents may produce an index that is outside the range of the array, possibly causing a crash or an exit in other environments.

Frequently Asked Questions

Want to get errata notifications? Sign up here.