CVE-2026-80969

Description

A flaw was found in the Linux kernel's ALSA mpu401 driver. The driver fails to validate the card index when a device is manually bound through the sysfs interface. This oversight can lead to an out-of-bounds memory access. A local attacker with appropriate permissions could exploit this vulnerability to cause a denial of service or potentially achieve privilege escalation.

Statement

A flaw was found in the Linux kernel's ALSA mpu401 driver as shipped in Red Hat Enterprise Linux (kernel and kernel-rt) and in OpenShift Container Platform via the RHEL CoreOS layers. The driver blindly trusts the card index (devptr->id) at probe time without checking that it is within the valid range. Devices the driver creates itself at module probe time are safe, but when a device is bound manually through the sysfs interface the index can be out of range (for example -1, used as "none"), which leads to an out-of-bounds access of the index[] array and other parameters. A local attacker with the elevated privileges required to bind devices via sysfs could exploit this out-of-bounds access to cause a denial of service (kernel crash) or potentially escalate privileges. Red Hat rated this flaw MODERATE severity with a CVSS 3.1 score of 5.5 (CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H); the impact is limited primarily to availability because exploitation requires local access with privileged sysfs device-binding operations. The fix is currently deferred for the affected Red Hat Enterprise Linux and OpenShift Container Platform streams because MODERATE-severity flaws with a CVSS score in this range do not meet the bar for an immediate kernel update; the residual risk until the fix is delivered is that a privileged local user who manually binds an mpu401 device through the sysfs interface could trigger the out-of-bounds access and crash the kernel.

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 Score5.5N/AN/A
Attack VectorLocalN/AN/A
Attack ComplexityLowN/AN/A
Privileges RequiredLowN/AN/A
User InteractionNoneN/AN/A
ScopeUnchangedN/AN/A
ConfidentialityNoneN/AN/A
Integrity ImpactNoneN/AN/A
Availability ImpactHighN/AN/A

Vector

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

Understanding the Weakness (CWE)

Confidentiality

Technical Impact: Read Memory

An attacker could get secret values such as cryptographic keys, PII, memory addresses, or other information that could be used in additional attacks.

Confidentiality

Technical Impact: Bypass Protection Mechanism

Out-of-bounds memory could contain memory addresses or other information that can be used to bypass ASLR and other protection mechanisms in order to improve the reliability of exploiting a separate weakness for code execution.

Availability

Technical Impact: DoS: Crash, Exit, or Restart

An attacker could cause a segmentation fault or crash by causing memory to be read outside of the bounds of the buffer. This is especially likely when the code reads a variable amount of data and assumes that a sentinel exists to stop the read operation, such as a NUL in a string.

Other

Technical Impact: Varies by Context

The read operation could produce other undefined or unexpected results.

Frequently Asked Questions

Want to get errata notifications? Sign up here.