CVE-2026-72262

Description

A flaw was found in the Advanced Linux Sound Architecture (ALSA) Sound Open Firmware (SOF) ipc3-control component of the Linux kernel. This vulnerability, a heap overflow, occurs due to incorrect bounds checks when handling user data lengths. An unprivileged local user can exploit this to write past allocated memory or read adjacent heap data, potentially leading to information disclosure or arbitrary code execution.

Mitigation

To mitigate this vulnerability, prevent the Sound Open Firmware kernel module from loading by blacklisting it in the modprobe configuration:

1. Create a configuration file to blacklist and disable autoloading of the module:
# echo "blacklist snd-sof" >> /etc/modprobe.d/snd-sof.conf
# echo "install snd-sof /bin/true" >> /etc/modprobe.d/snd-sof.conf

2. If the module is already loaded, a system reboot is required for the configuration to take effect:
# reboot

Caveats: Applying this workaround will disable audio functionality on hardware platforms that depend on the Sound Open Firmware (SOF) driver subsystem.

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).

CVSS v3 Score Breakdown

Red HatNVDcve.org
Base Score7N/A7.8
Attack VectorLocalN/ALocal
Attack ComplexityHighN/ALow
Privileges RequiredLowN/ALow
User InteractionNoneN/ANone
ScopeUnchangedN/AUnchanged
ConfidentialityHighN/AHigh
Integrity ImpactHighN/AHigh
Availability ImpactHighN/AHigh

Vector

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

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

Understanding the Weakness (CWE)

Integrity

Technical Impact: Modify Memory; Execute Unauthorized Code or Commands

Write operations could cause memory corruption. In some cases, an adversary can modify control data such as return addresses in order to execute unexpected code.

Availability

Technical Impact: DoS: Crash, Exit, or Restart

Attempting to access out-of-range, invalid, or unauthorized memory could cause the product to crash.

Other

Technical Impact: Unexpected State

Subsequent write operations can produce undefined or unexpected results.

Frequently Asked Questions

Want to get errata notifications? Sign up here.