ASoC: SOF: ipc4-pcm: Continue the pipeline trigger in case of IPC timeout
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
6ee66295542f88e5179439f60053de792df3f90e| No fix yet |
| Linux Linux |
|
|
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.
From the CVE record · Linux
The Linux kernel’s ASoC SOF ipc4-pcm pipeline trigger can fail to continue state changes after a firmware crash or IPC timeout. This can leave the kernel’s internal pipeline state unable to reset correctly for the next DSP boot. The input does not describe an attacker path, authentication requirements, or user interaction.
Engineers running Linux kernels with ASoC SOF ipc4-pcm should check their exposure; affected versions are not specified.