# CVE-2026-64243: ASoC: codecs: simple-mux: Fix enum control bounds check

> An integer overflow in the Linux kernel's simple-mux codec allows invalid enum values, potentially leading to out-of-bounds reads and code execution.

- **Severity:** High 7.1 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 24 Jul 2026
- **Updated:** 19 Oct 2026
- **Also known as:** BELL-CVE-2026-64243, DEBIAN-CVE-2026-64243, GHSA-g8x3-7685-9cvh, ROOT-OS-UBUNTU-2204-CVE-2026-64243, UBUNTU-CVE-2026-64243

## What is CVE-2026-64243?

CVE-2026-64243 is a high-severity vulnerability in Linux kernel, published on 24 Jul 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official 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.

Weakness: CWE-129 (Improper Validation of Array Index), CWE-125 (Out-of-bounds Read)

## Which versions are affected by CVE-2026-64243?

It affects 1 product.


Products: Linux kernel.

## How do I fix CVE-2026-64243?

Apply the vendor's patch.

## Is CVE-2026-64243 being exploited?

There is no known exploitation of CVE-2026-64243 in the wild and no public exploit code.

## Other vulnerabilities in Linux kernel

- [CVE-2026-53266](https://insights.sbomify.com/CVE-2026-53266/): Linux Kernel Out-of-Bounds Write (high 8.8, exploited in the wild)
- [CVE-2013-6282](https://insights.sbomify.com/CVE-2013-6282/): Linux Kernel Improper Input Validation (high 8.8, exploited in the wild)
- [CVE-2022-0185](https://insights.sbomify.com/CVE-2022-0185/): Linux Kernel Heap-Based Buffer Overflow (high 8.4, exploited in the wild)
- [CVE-2013-2094](https://insights.sbomify.com/CVE-2013-2094/): Linux Kernel Privilege Escalation (high 8.4, exploited in the wild)
- [CVE-2026-53362](https://insights.sbomify.com/CVE-2026-53362/): Linux Kernel Unspecified (high 7.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-64243 and fix it if it is affected.

What it is: CVE-2026-64243 is a high-severity vulnerability in Linux kernel, published on 24 Jul 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-64243 in the wild and no public exploit code.

Affected product: Linux kernel. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-64243/ (Markdown: https://insights.sbomify.com/CVE-2026-64243/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-64243
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-64243
- OSV: https://osv.dev/vulnerability/CVE-2026-64243

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-64243/
Summaries are generated and may contain mistakes; the official description above is the record.