Linux vulnerability

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.

Published 15 Aug 2026Updated 3 Oct 20265 sources
CVSS 0.0

What happened

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.

Affected versions

Linux: 64527e8a352968bda529f01df1c9dd5fe581ff04 through before c405b07246bf179e9457de57501c3470175b165e (git); 64527e8a352968bda529f01df1c9dd5fe581ff04 through before 473f7d25d93e80db526a9d05887f0071abdc6d9b (git); 64527e8a352968bda529f01df1c9dd5fe581ff04 through before 5c2537cf24d673956b4e58029001667f89586fa2 (git); 64527e8a352968bda529f01df1c9dd5fe581ff04 through before ba37b62ed0a443b8e23f53a7477e7f2537fd34c7 (git); 64527e8a352968bda529f01df1c9dd5fe581ff04 through before b7e44d1986d6671342c19b82192189ca5db5dab7 (git); 4.6 Fixed: See vendor advisory.

Why it matters

Review the vendor advisory and exposure of the affected product to determine operational impact.

Detection & mitigation

  • Apply vendor-provided updates or mitigations.
  • Review affected product exposure and access logs.

Public PoC references

No public PoC reference has passed the current publication threshold.