Unsafe allocation via unchecked topology volume ranges
Published Sep 17, 2026 · Updated Sep 17, 2026
Range validation errors in Linux SOF topology loading allow attackers to cause unsafe allocation and indexing via crafted mixer data. In sound/soc/sof/topology.c, sof_control_load_volume stores unchecked mixer bounds in signed fields and passes max + 1 through an int allocation argument without rejecting inverted ranges or maxima at or above INT_MAX. Triggering requires SOF to load attacker-controlled topology data; Amazon Linux assesses high local privileges, but no specific crash mode is documented.
Summary
What happened
Range validation errors in Linux SOF topology loading allow attackers to cause unsafe allocation and indexing via crafted mixer data. In sound/soc/sof/topology.c, sof_control_load_volume stores unchecked mixer bounds in signed fields and passes max + 1 through an int allocation argument without rejecting inverted ranges or maxima at or above INT_MAX. Triggering requires SOF to load attacker-controlled topology data; Amazon Linux assesses high local privileges, but no specific crash mode is documented.
The record
- CVE
- CVE-2026-90196
- Published
- Sep 17, 2026
- Updated
- Sep 17, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- Unavailable
- Attack vector
- Unavailable
- Privileges
- Unavailable
Timeline
How it unfolded
- Sep 17, 2026CVE publishedPublication date reported by the CVE source.
- Sep 17, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=311ce4fe7637d96608b6e57bf9ebbd8aabcf429e <72d0b77412aef2cec554cc84e176658f2a48dafa
- Affected versionversion=311ce4fe7637d96608b6e57bf9ebbd8aabcf429e <8e1d63f5e272061208455b5aa4cc0d5bcbe5c1a8
- Affected versionversion=311ce4fe7637d96608b6e57bf9ebbd8aabcf429e <992e130b888699d18da901b593d7a0fb75041a03
- Affected versionversion=311ce4fe7637d96608b6e57bf9ebbd8aabcf429e <a698e4a60fa54268a38f4e66378851a196cb139b
- Affected versionversion=311ce4fe7637d96608b6e57bf9ebbd8aabcf429e <cd63a1eb677e9548ba2d512be5dac4cb474ae145
- Affected versionversion=311ce4fe7637d96608b6e57bf9ebbd8aabcf429e <d2f41287b51a3261d447ae38000f7a6f5860663a
- Affected versionversion=5.2
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Activity data is delayed. The latest report is Sep 28, 2026.
Weakness, pattern, technique
No sourced classifications are available.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Get started