CVE-2026-74293

Description

A flaw was found in the Linux kernel's Advanced Linux Sound Architecture System on Chip (ASoC) subsystem, specifically within the fsl_audmix component. The fsl_audmix_put_mix_clk_src() and fsl_audmix_put_out_src() functions do not properly validate user-provided enum values before processing them. This improper validation could allow a local attacker to supply out-of-range values, potentially leading to unexpected system behavior or a denial of service.

Statement

Red Hat Enterprise Linux 9 and 10 are affected by a moderate-severity flaw in the Linux kernel ASoC (ALSA System-on-Chip) Freescale fsl_audmix driver. The fsl_audmix_put_mix_clk_src() and fsl_audmix_put_out_src() ALSA control callbacks convert a user-supplied enum item with snd_soc_enum_item_to_val() before checking whether the item is within the enum's item count. A local attacker with permission to write the affected audio mixer controls can therefore supply an out-of-range enum value: in the clock-source path the converted value is used in BIT() logic, and in the output-source path it is used as an index into the prm transition table, resulting in an out-of-bounds read and potential kernel crash or denial of service. Red Hat rates this flaw Moderate (CVSS 3.1: 5.5, AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H) because the available evidence supports only an availability impact; the upstream CVE record assigns a higher score (7.8) with high confidentiality and integrity impacts, which the technical evidence for this flaw does not support. Within the affected Red Hat Enterprise Linux 9 and 10 kernel and kernel-rt packages the fix is currently deferred, reflecting the moderate severity and the constrained exploitability: exploitation requires local access with permission to write the affected ALSA mixer controls on systems using the Freescale fsl_audmix audio mixer hardware, so the residual risk is limited to local denial of service on such systems. Red Hat Enterprise Linux 6, 7, and 8 and Red Hat In-Vehicle OS are not affected because the vulnerable code is not present in those product streams.

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/A7.8
Attack VectorLocalN/ALocal
Attack ComplexityLowN/ALow
Privileges RequiredLowN/ALow
User InteractionNoneN/ANone
ScopeUnchangedN/AUnchanged
ConfidentialityNoneN/AHigh
Integrity ImpactNoneN/AHigh
Availability ImpactHighN/AHigh

Vector

Red Hat: 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:H/I:H/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.