CVE-2026-80581: ASoC: SOF: ipc4-pcm: Continue the pipeline trigger in case of IPC timeout
In the Linux kernel, the following vulnerability has been resolved:
ASoC: SOF: ipc4-pcm: Continue the pipeline trigger in case of IPC timeout
Ignore IPC errors for pipeline state change if the firmware state is crashed or the IPC has timed out.
If the firmware has crashed the kernel still needs to go through the state changes to reset its internal to be able to correctly work the next time the DSP is booted up.
The case with IPC timeout is a bit more problematic, but it has been rootcaused to be the result of system scheduling blockage and the firmware did actually received and handled the message, but the reply handling got blocked by issues outside of the SOF stack. So far the best way to handle this is to continue with setting the state.
Affected Software
Event History
Frequently Asked Questions
Does an IPC timeout mean the DSP firmware did not receive the pipeline state-change request?
Not necessarily. The timeout has been root-caused to system scheduling blockage outside the SOF stack; the firmware may have received and handled the message while reply handling was blocked.
Why must pipeline state changes continue after a firmware crash?
The kernel must complete its internal state transitions so it can reset its state correctly and work properly when the DSP is booted again.