# CVE-2026-90068: ASoC: dapm: Fix off-by-one check on the second enum channel

> An off-by-one error in the Linux kernel ASoC DAPM enum handler allows local attackers to read out-of-bounds memory or cause a crash.

- **Severity:** Not scored
- **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:** 17 Sep 2026
- **Updated:** 19 Oct 2026
- **Also known as:** AZL-101984, BELL-CVE-2026-90068, DEBIAN-CVE-2026-90068, GHSA-gx3g-862r-xxh6, UBUNTU-CVE-2026-90068

## What is CVE-2026-90068?

CVE-2026-90068 is a vulnerability in Linux, published on 17 Sep 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: dapm: Fix off-by-one check on the second enum channel

The snd_soc_dapm_put_enum_double() rejects item[0] once it reaches
e->items, but it lets item[1] be equal to it.  Both go on to
snd_soc_enum_item_to_val(), which indexes e->values with no bound of
its own, so an enum with a value table reads one element past the end.

The indexing arrived with the MUX consolidation, which relaxed the
item[1] check in the same hunk.  The value MUX handler it deleted used
>= there, and the snd_soc_put_enum_double() in soc-ops.c still does.

Only adav80x pairs a value table with two shifts, and its second
channel looks accidental, but the control does report two values.
Writing three into it reads off the end of adav80x_mux_values.  The
core catches that only under CONFIG_SND_CTL_INPUT_VALIDATION, which
defaults off.

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


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

Apply the vendor's patch.

## Is CVE-2026-90068 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-90068 is a vulnerability in Linux, published on 17 Sep 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-90068 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-90068/ (Markdown: https://insights.sbomify.com/CVE-2026-90068/index.md)
```

## Sources

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

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