The bug in the ASoC SOF IPC4 topology causes a cached copier widget payload to be reused after suspend and resume cycles without rebuilding. The payload contains DMA channel identifiers that may have changed, leading to channel conflicts in the firmware. When the firmware receives this stale information it corrupts DMA state and crashes, halting audio functionality. The weakness is exemplified by concurrent data misuse (CWE-367).

This vulnerability impacts the audio subsystem of the Linux kernel across all distributions that include the affected ASoC SOF code path before the patch referenced in the listed git commits. Essentially, any host that runs the kernel with the buggy ipc4 topology implementation is potentially affected, regardless of vendor, as it is a core kernel component.

The CVSS score of 5.5 indicates a moderate severity, while an EPSS score of less than 1% suggests a low likelihood of exploitation. The vulnerability is not listed in the CISA KEV catalog, further indicating limited known exploitation. The likely attack vector is local: an attacker would need to trigger audio suspend/resume cycles or otherwise interact with the kernel’s audio driver to cause the stale payload to be sent. This inference follows from the description of the bug, which is triggered only during legitimate suspend/resume operations.