# CVE-2026-74295: ASoC: codecs: hdac_hdmi: Validate written enum value

> An out-of-bounds read in the Linux kernel HDMI audio driver allows attackers to read memory or crash the system via invalid enum values.

- **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:** 15 Aug 2026
- **Updated:** 16 Oct 2026
- **Also known as:** BELL-CVE-2026-74295, DEBIAN-CVE-2026-74295, GHSA-gpjf-6x9p-w663, UBUNTU-CVE-2026-74295

## What is CVE-2026-74295?

CVE-2026-74295 is a high-severity memory corruption 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: codecs: hdac_hdmi: Validate written enum value

hdac_hdmi_set_pin_port_mux() uses the written enum value to index the
texts array before calling snd_soc_dapm_put_enum_double(), which validates
that the value is within the enum item range.

An out-of-range value can therefore make the driver read past the texts
array before the helper rejects the write. Move the lookup after the helper
has accepted the value.

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


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

Apply the vendor's patch.

## Is CVE-2026-74295 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-74295 is a high-severity memory corruption 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-74295 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-74295/ (Markdown: https://insights.sbomify.com/CVE-2026-74295/index.md)
```

## Sources

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

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