ASoC: SOF: validate topology volume range before allocation (CVE-2026-90196) | HOL Guard CVE

Unknown severity · Source severity not reportedCVE-2026-90196

ASoC: SOF: validate topology volume range before allocation

Answer in brief

CVE-2026-90196 records a Unknown severity vulnerability in ASoC: SOF: validate topology volume range before allocation. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.

Analysis pending evidence review

HOL Guard separates source facts from reviewed analysis. See the methodology.

Published Sep 17, 2026Updated Sep 17, 2026Source checked Sep 17, 2026First seen by HOL Sep 17, 2026Material review Sep 17, 2026

Upstream Advisory

Key facts

Risk: Unknown severitySource severity not reported
Exploitation: Not marked as known exploited
Affected software: 2 mapped packages or products
Fix availability: Available

Why this deserves its current priority

A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
Linux/Linuxgeneric	>=311ce4fe7637d96608b6e57bf9ebbd8aabcf429e <992e130b888699d18da901b593d7a0fb75041a03 \|\| >=311ce4fe7637d96608b6e57bf9ebbd8aabcf429e <cd63a1eb677e9548ba2d512be5dac4cb474ae145 \|\| >=311ce4fe7637d96608b6e57bf9ebbd8aabcf429e <8e1d63f5e272061208455b5aa4cc0d5bcbe5c1a8 \|\| >=311ce4fe7637d96608b6e57bf9ebbd8aabcf429e <d2f41287b51a3261d447ae38000f7a6f5860663a \|\| >=311ce4fe7637d96608b6e57bf9ebbd8aabcf429e <72d0b77412aef2cec554cc84e176658f2a48dafa \|\| >=311ce4fe7637d96608b6e57bf9ebbd8aabcf429e <a698e4a60fa54268a38f4e66378851a196cb139b	992e130b888699d18da901b593d7a0fb75041a03, cd63a1eb677e9548ba2d512be5dac4cb474ae145, 8e1d63f5e272061208455b5aa4cc0d5bcbe5c1a8, d2f41287b51a3261d447ae38000f7a6f5860663a, 72d0b77412aef2cec554cc84e176658f2a48dafa, a698e4a60fa54268a38f4e66378851a196cb139b
Linux/Linuxgeneric	5.2	Not reported

Recommended response

Check inventory. Check lockfiles and deployed manifests for Linux/Linux, Linux/Linux.
Review the reported fix. Update Linux/Linux to 992e130b888699d18da901b593d7a0fb75041a03 if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

Published upstream
Sep 17, 2026
Evidence: source:cvelist:source_dates:source-dates:record
Source modified
Sep 17, 2026
Evidence: source:cvelist:source_dates:source-dates:record
First seen by HOL
Sep 17, 2026

Sources and claim methodology

Upstream source 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.

Quoted source text, attributed separately from HOL analysis.