CVE-2026-80581

ASoC: SOF: ipc4-pcm: Continue the pipeline trigger in case of IPC timeout

N/A
Published: August 26, 2026 at 02:37 PM UTC
Updated: October 30, 2026 at 01:20 PM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 0.2%

Description

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

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

3cac6eebea9b4bc5f041e157e45c76e212ad67596.6.236.7.116.8c40aad7c81e5fba34b70123ed7ce3397fa62a4d2d153e8b154f9746ac969c85a4e6474760453647c
Vendor states this is fixed in 17661c67b206612cb3ba65d5ae726cd2015d0a53 (fixed)
Vendor states this is fixed in 4931c09d83877dc350106bae745321c3f295129b (fixed)
Vendor states this is fixed in 6b512a5330ef1a41db7aff4b80c4e952b8d52f17 (fixed)
Vendor states this is fixed in f2435a46dfa1a5693cf2664afd022db66ee58121 (fixed)
Vendor states this is fixed in 6.12.114 (unaffected)
Vendor states this is fixed in 6.18.46 (unaffected)
Vendor states this is fixed in 6.6.154 (unaffected)
Vendor states this is fixed in 6.8 (unaffected)
Vendor states this is fixed in 7.1.10 (unaffected)
Vendor states this is fixed in 7.2 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

Quick Info

StatusRECEIVED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card