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.
Fix
Nothing published yet: no patch, vendor advisory or mitigation reference on NVD, no vendor advisory in the News for this CVE, not in CISA's KEV, no fixed package version. BaselineWatch does not guess at one.
Change history 3
- StatusReceived → PublishedNVD modified 2026-10-21 12:46
- StatusPublished → ReceivedNVD modified 2026-10-21 13:19
- First seenunscored · linuxNVD modified 2026-10-21 12:46
Affected (CPE criteria) 0
NVD has not attached CPE configurations yet.
References 5
- https://git.kernel.org/stable/c/17661c67b206612cb3ba65d5ae726cd2015d0a53
- https://git.kernel.org/stable/c/4931c09d83877dc350106bae745321c3f295129b
- https://git.kernel.org/stable/c/6b512a5330ef1a41db7aff4b80c4e952b8d52f17
- https://git.kernel.org/stable/c/96d51b8c5a909937d41f9c03495188d4190f877d
- https://git.kernel.org/stable/c/f2435a46dfa1a5693cf2664afd022db66ee58121