# CVE-2026-72415: ASoC: SDCA: Validate written enum value in ge_put_enum_double()

> A local attacker can trigger an out-of-bounds read in the Linux kernel SDCA audio driver by supplying an invalid enum index, potentially leaking heap memory.

- **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:** DEBIAN-CVE-2026-72415, GHSA-cq9w-mfcc-7q5j, UBUNTU-CVE-2026-72415

## What is CVE-2026-72415?

CVE-2026-72415 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: SDCA: Validate written enum value in ge_put_enum_double()

ge_put_enum_double() passes the user-supplied enumeration index
item[0] to snd_soc_enum_item_to_val() without checking it against the
number of items in the enum:

	ret = snd_soc_enum_item_to_val(e, item[0]);

snd_soc_enum_item_to_val() indexes the heap-allocated e->values[] array
with that index (e->values is set from a devm_kcalloc() of e->items
entries), so a control write with an out-of-range item[0] reads past the
end of the values buffer.  The bounds check in
snd_soc_dapm_put_enum_double() only runs afterwards, so it does not
prevent the read here.

Reject an out-of-range item before using it, matching the other enum put
handlers.

This issue was pointed out by the Sashiko AI review bot while reviewing a
related enum-validation series:
https://lore.kernel.org/all/20260609125735.CEB651F00893@smtp.kernel.org/

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


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

Apply the vendor's patch.

## Is CVE-2026-72415 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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