CVE-2026-80581: Linux kernel · ASoC: SOF: ipc4-pcm: Continue the pipeline trigger in case of IPC timeout
Affects Linux kernelSource CVE Database V5
Not known to be exploited · fixed in f2435a46dfa1a5693cf2664afd022db66ee58121 : update Linux kernel when convenient.
Data as of 26 Oct 2026, 13:47 UTC
Rated by Threat Radar · CVSS not yet scored by NVD
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 10% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in f2435a46dfa1a5693cf2664afd022db66ee58121, 17661c67b206612cb3ba65d5ae726cd2015d0a53, 4931c09d83877dc350106bae745321c3f295129b +4
Exploitation evidence
Disclosed: evidence found.
CVE published 26 Aug 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in– |
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.
References
- git.kernel.org/stable/c/4931c09d83877dc350106bae745321c3f295129b (opens in a new tab)
- git.kernel.org/stable/c/96d51b8c5a909937d41f9c03495188d4190f877d (opens in a new tab)
- git.kernel.org/stable/c/f2435a46dfa1a5693cf2664afd022db66ee58121 (opens in a new tab)
- git.kernel.org/stable/c/6b512a5330ef1a41db7aff4b80c4e952b8d52f17 (opens in a new tab)
- git.kernel.org/stable/c/17661c67b206612cb3ba65d5ae726cd2015d0a53 (opens in a new tab)