CVE-2026-90196: ASoC: SOF: validate topology volume range before allocation
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 INTMAX cannot be represented safely after the increment or in the signed fields. Validate the complete range before storing it or allocating the table.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
debian/linuxto a version that resolves this vulnerability.Fixed in 6.1.190-1Fixed in 6.12.115-2Fixed in 7.2.12-1Fixed in 7.2.15-1 - Upgrade
Upgrade
debian/linux-6.12to a version that resolves this vulnerability.Fixed in 6.12.113-1~deb12u1 - Upgrade
Upgrade
ubuntu/linux-hwe-7.0to a version that resolves this vulnerability.Fixed in 7.0.0-42.42~24.04.1 - Upgrade
Upgrade
ubuntu/linux-riscv-7.0to a version that resolves this vulnerability.Fixed in 7.0.0-42.42.1~24.04.1 - Upgrade
Upgrade
ubuntu/linuxto a version that resolves this vulnerability.Fixed in 7.0.0-42.42 - Upgrade
Upgrade
ubuntu/linux-awsto a version that resolves this vulnerability.Fixed in 7.0.0-1016.17 - Upgrade
Upgrade
ubuntu/linux-gcpto a version that resolves this vulnerability.Fixed in 7.0.0-1016.18 - Upgrade
Upgrade
ubuntu/linux-ibmto a version that resolves this vulnerability.Fixed in 7.0.0-1017.17 - Upgrade
Upgrade
ubuntu/linux-oem-7.0to a version that resolves this vulnerability.Fixed in 7.0.0-1017.17 - Upgrade
Upgrade
ubuntu/linux-oracleto a version that resolves this vulnerability.Fixed in 7.0.0-1015.16 - Upgrade
Upgrade
ubuntu/linux-riscvto a version that resolves this vulnerability.Fixed in 7.0.0-42.42.1 - Compensating control
Validate the complete SOF topology mixer volume range before storing it or allocating the volume table: reject inverted ranges and reject any maximum value at or above INT_MAX.
Event History
Frequently Asked Questions
What inputs make the affected code unsafe?
A topology mixer volume range is unsafe when its minimum exceeds its maximum, or when its maximum is at least INT_MAX. The code uses these values as non-negative volume-table indices, but stores them in signed fields and allocates max + 1 entries through an int argument.
What does the fix change?
The fix validates the complete topology volume range before storing the values or allocating the volume table. This prevents invalid inverted ranges and maximum values that cannot be safely incremented or represented.
How can I identify potentially affected topology data?
Review SOF topology mixer definitions for volume ranges with min greater than max or max values at or above INT_MAX. Those ranges should be treated as invalid until the resolved kernel change is present.