ASoC: SOF: ipc4-pcm: Continue the pipeline trigger in case of IPC timeout (CVE-2026-80581) | HOL Guard CVE

Unknown severity · Source severity not reportedCVE-2026-80581

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

Answer in brief

CVE-2026-80581 records a Unknown severity vulnerability in ASoC: SOF: ipc4-pcm: Continue the pipeline trigger in case of IPC timeout. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.

Analysis pending evidence review

HOL Guard separates source facts from reviewed analysis. See the methodology.

Published Aug 26, 2026Updated Aug 26, 2026Source checked Aug 26, 2026First seen by HOL Aug 26, 2026Material review Aug 26, 2026

Upstream Advisory

Key facts

Risk: Unknown severitySource severity not reported
Exploitation: Not marked as known exploited
Affected software: 2 mapped packages or products
Fix availability: Available

Why this deserves its current priority

A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
Linux/Linuxgeneric	>=c40aad7c81e5fba34b70123ed7ce3397fa62a4d2 <f2435a46dfa1a5693cf2664afd022db66ee58121 \|\| >=c40aad7c81e5fba34b70123ed7ce3397fa62a4d2 <6b512a5330ef1a41db7aff4b80c4e952b8d52f17 \|\| >=c40aad7c81e5fba34b70123ed7ce3397fa62a4d2 <17661c67b206612cb3ba65d5ae726cd2015d0a53 \|\| 3cac6eebea9b4bc5f041e157e45c76e212ad6759 \|\| d153e8b154f9746ac969c85a4e6474760453647c \|\| >=6.6.23 <6.7 \|\| >=6.7.11 <6.8	f2435a46dfa1a5693cf2664afd022db66ee58121, 6b512a5330ef1a41db7aff4b80c4e952b8d52f17, 17661c67b206612cb3ba65d5ae726cd2015d0a53, 6.7, 6.8
Linux/Linuxgeneric	6.8	Not reported

Recommended response

Check inventory. Check lockfiles and deployed manifests for Linux/Linux, Linux/Linux.
Review the reported fix. Update Linux/Linux to f2435a46dfa1a5693cf2664afd022db66ee58121 if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

Published upstream
Aug 26, 2026
Evidence: source:cvelist:source_dates:source-dates:record
Source modified
Aug 26, 2026
Evidence: source:cvelist:source_dates:source-dates:record
First seen by HOL
Aug 26, 2026

Sources and claim methodology

Upstream source 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.

Quoted source text, attributed separately from HOL analysis.