# CVE-2026-74294: ASoC: meson: aiu: Validate written enum values

> The Linux kernel AIU audio driver fails to validate enum values before conversion, potentially leading to undefined behavior or memory issues.

- **Severity:** High 7.3 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:L/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-74294, DEBIAN-CVE-2026-74294, GHSA-wv7f-69g8-fhc5, UBUNTU-CVE-2026-74294

## What is CVE-2026-74294?

CVE-2026-74294 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: meson: aiu: Validate written enum values

The AIU HDMI and internal codec mux put callbacks use the written enum
value with snd_soc_enum_item_to_val() before checking whether the value is
valid for the enumeration.

Reject out-of-range values before converting the enum item, matching the
validation already done by the G12A HDMI and internal codec mux controls.

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


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

Apply the vendor's patch.

## Is CVE-2026-74294 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-74294 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-74294 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-74294/ (Markdown: https://insights.sbomify.com/CVE-2026-74294/index.md)
```

## Sources

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

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