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

> A flaw in the Linux kernel's SOF audio driver causes denial of service when IPC timeouts occur, requiring a patch to ensure proper state recovery.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 26 Aug 2026
- **Updated:** 21 Oct 2026
- **Also known as:** AZL-97725, BELL-CVE-2026-80581, DEBIAN-CVE-2026-80581, GHSA-5rgw-cxhj-rmhq, UBUNTU-CVE-2026-80581

## What is CVE-2026-80581?

CVE-2026-80581 is a denial of service vulnerability in Linux, published on 26 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.

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

## Which versions are affected by CVE-2026-80581?


## How do I fix CVE-2026-80581?

Apply the vendor's patch.

## Is CVE-2026-80581 being exploited?

There is no known exploitation of CVE-2026-80581 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-80581 and fix it if it is affected.

What it is: CVE-2026-80581 is a denial of service vulnerability in Linux, published on 26 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-80581 in the wild and no public exploit code.

Affected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-80581/ (Markdown: https://insights.sbomify.com/CVE-2026-80581/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-80581
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-80581
- OSV: https://osv.dev/vulnerability/CVE-2026-80581

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-80581/
Summaries are generated and may contain mistakes; the official description above is the record.