# CVE-2026-80910: ASoC: codecs: lpass-wsa-macro: Fix enum kcontrol accesses

> Local attackers can cause audio control failures in the Linux kernel when debug configurations are enabled due to incorrect enum access types.

- **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:** 4 Sep 2026
- **Updated:** 4 Sep 2026
- **Also known as:** AZL-99549, BELL-CVE-2026-80910, DEBIAN-CVE-2026-80910, GHSA-5q4c-hcqg-2qj6, UBUNTU-CVE-2026-80910

## What is CVE-2026-80910?

CVE-2026-80910 is a vulnerability in Linux, published on 4 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: codecs: lpass-wsa-macro: Fix enum kcontrol accesses

EAR SPKR PA Gain" and the four "WSA RX* Mux" controls are enumerated,
but their get and put callbacks access the value through
ucontrol->value.integer.value[0] (a long) instead of
ucontrol->value.enumerated.item[0] (an unsigned int).

This same pattern was fixed in the sibling drivers by
commit bcfe5f76cc40 ("ASoC: codecs: rx-macro: fix accessing array
out of bounds for enum type") and
commit 0ea5eff7c606 ("ASoC: codecs: va-macro: fix accessing array
out of bounds for enum type"), but wsa-macro was missed.

On 64-bit kernels with CONFIG_SND_CTL_DEBUG this trips the elem value
sanity check and every read of these controls fails with -EINVAL.

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


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

Apply the vendor's patch.

## Is CVE-2026-80910 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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