ASoC: SOF: validate topology volume range before allocation
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 6.1.188, 6.6.157, 6.12.110, 6.18.52, 7.2.6
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
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.
Timeline
- CVE published
- Record last updated
Affected versions
- Linux Linux
From 311ce4fe7637d96608b6e57bf9ebbd8aabcf429e · fixed in 992e130b888699d18da901b593d7a0fb75041a03; From 311ce4fe7637d96608b6e57bf9ebbd8aabcf429e · fixed in cd63a1eb677e9548ba2d512be5dac4cb474ae145; From 311ce4fe7637d96608b6e57bf9ebbd8aabcf429e · fixed in 8e1d63f5e272061208455b5aa4cc0d5bcbe5c1a8; From 311ce4fe7637d96608b6e57bf9ebbd8aabcf429e · fixed in d2f41287b51a3261d447ae38000f7a6f5860663a; From 311ce4fe7637d96608b6e57bf9ebbd8aabcf429e · fixed in 72d0b77412aef2cec554cc84e176658f2a48dafa; From 311ce4fe7637d96608b6e57bf9ebbd8aabcf429e · fixed in a698e4a60fa54268a38f4e66378851a196cb139b
- Linux Linux
5.2
- KernelLinux
From 5.2.0 · fixed in 6.1.188; From 6.2.0 · fixed in 6.6.157; From 6.7.0 · fixed in 6.12.110; From 6.13.0 · fixed in 6.18.52; From 6.19.0 · fixed in 7.2.6