CVE-2026-64243
Received Received - Intake

Buffer Overflow in Linux Kernel ASoC Simple-Mux Driver

Publication date: 2026-07-24

Last updated on: 2026-07-24

Assigner: kernel.org

Description
In the Linux kernel, the following vulnerability has been resolved: ASoC: codecs: simple-mux: Fix enum control bounds check simple_mux_control_put() rejects values greater than e->items, but enum control values are zero based. For the two-entry mux used by this driver, valid values are 0 and 1, so value 2 must be rejected as well. Accepting e->items can store an invalid mux state, pass it to the GPIO setter, and pass it on to the DAPM mux update path where it is used as an index into the enum text array. Use the same >= e->items check used by the ASoC enum helpers.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-07-24
Last Modified
2026-07-24
Generated
2026-07-24
AI Q&A
2026-07-24
EPSS Evaluated
N/A
NVD
CVE-2026-64243
EUVD
EUVD-2026-48652

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
linux linux_kernel *

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-UNKNOWN

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This is a vulnerability in the Linux kernel's ASoC (ALSA System on Chip) subsystem. It involves a bounds check error in the simple-mux codec driver. The function simple_mux_control_put incorrectly allows enum control values equal to or greater than the number of available items, which can lead to invalid mux states being set. This happens because enum control values are zero-based, so for a two-entry mux, only 0 and 1 are valid, but the function may accept 2 or higher.

Detection Guidance

This vulnerability is specific to the Linux kernel's ASoC (ALSA System on Chip) subsystem, particularly in the simple-mux codec driver. Detection requires checking the kernel version and examining the affected driver code. Use commands like 'uname -a' to check the kernel version and 'grep simple_mux_control_put /path/to/kernel/sources' to inspect the driver code for the vulnerable function.

Impact Analysis

This vulnerability could allow an attacker with local access to cause undefined behavior in the audio subsystem. Specifically, it might lead to memory corruption or crashes by passing invalid indices to the DAPM mux update path. This could disrupt audio functionality or potentially escalate privileges if exploited.

Compliance Impact

This vulnerability does not directly affect compliance with GDPR, HIPAA, or similar standards. It is a low-level Linux kernel issue related to audio subsystem controls, which does not involve data privacy, security, or protected health information handling.

Mitigation Strategies

Apply the latest kernel update from your Linux distribution to patch the vulnerability. If a patch is not yet available, consider disabling the affected driver module (simple_mux) if not required. Monitor vendor advisories for updates and test the patch in a non-production environment before full deployment.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-64243. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart