# CVE-2026-90196: ASoC: SOF: validate topology volume range before allocation

> An integer overflow in the Linux kernel's SOF audio driver allows attackers to cause denial of service or potentially execute code via malformed topology data.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **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-102272, BELL-CVE-2026-90196, DEBIAN-CVE-2026-90196, GHSA-2323-3q6r-jp65, UBUNTU-CVE-2026-90196

## What is CVE-2026-90196?

CVE-2026-90196 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: SOF: validate topology volume range before allocation

SOF treats the topology mixer min and max values as non-negative indices
into its volume table. It stores them in signed fields, allocates max + 1
entries through an int argument, and later indexes the table with the
stored range.

An inverted range is invalid, while a maximum at or above INT_MAX cannot
be represented safely after the increment or in the signed fields.
Validate the complete range before storing it or allocating the table.

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


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

Apply the vendor's patch.

## Is CVE-2026-90196 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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