# CVE-2026-74293: ASoC: fsl: fsl_audmix: Validate written enum values

> Missing validation of enum values in the Linux kernel fsl_audmix driver allows out-of-bounds access, potentially leading to crashes or code execution.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/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:** 15 Aug 2026
- **Updated:** 16 Oct 2026
- **Also known as:** BELL-CVE-2026-74293, DEBIAN-CVE-2026-74293, GHSA-p8cv-f9j9-548c, UBUNTU-CVE-2026-74293

## What is CVE-2026-74293?

CVE-2026-74293 is a high-severity vulnerability in Linux, published on 15 Aug 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: fsl: fsl_audmix: Validate written enum values

fsl_audmix_put_mix_clk_src() and fsl_audmix_put_out_src()
convert the user-provided enum item with snd_soc_enum_item_to_val()
before checking whether the item is within the enum's item count.

The generic snd_soc_put_enum_double() helper performs that
validation, but these callbacks use the converted value first: the
clock-source path tests it with BIT(), and the output-source path
indexes the prms transition table with it.

Reject out-of-range enum items before converting them.

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


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

Apply the vendor's patch.

## Is CVE-2026-74293 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-74293 is a high-severity vulnerability in Linux, published on 15 Aug 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-74293 in the wild and no public exploit code.

Affected product: Linux. 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-74293/ (Markdown: https://insights.sbomify.com/CVE-2026-74293/index.md)
```

## Sources

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

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