ASoC: topology: Check PCM and DAI name strings before use
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 64527e8a352968bda529f01df1c9dd5fe581ff04 · < b7e44d1986d6671342c19b82192189ca5db5dab7| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
ASoC: topology: Check PCM and DAI name strings before use
Topology objects store several PCM and DAI names in fixed-size UAPI arrays. Other topology parser paths validate these fields with bounded strnlen() checks before using them as C strings, but the PCM and DAI paths still pass some fixed-size arrays directly to strlen(), devm_kstrdup(), DAI lookup, and diagnostic prints.
A malformed topology blob with a non-NUL-terminated PCM, DAI, or stream capability name can therefore make the parser read past the end of the fixed-size field.
Reject unterminated PCM and DAI name fields before consuming them as C strings.
From the CVE record · Linux
The Linux kernel ASoC topology parser can read past a fixed-size name field when processing a malformed topology blob with an unterminated PCM, DAI, or stream capability name. The input does not specify whether an attacker needs local access, authentication, or user interaction to trigger this.
Engineers running Linux kernels with ASoC topology support should check their kernel; affected versions are not specified.