CVE-2026-80581: ASoC: SOF: ipc4-pcm: Continue the pipeline trigger in case of IPC timeout
Published Aug 26, 2026
·Updated
ASoC: SOF: ipc4-pcm: Continue the pipeline trigger in case of IPC timeout
Affected Software
2 affected componentsFixes available
Linux Linux kernel
Microsoft azl3 kernel 6.6.152.1-1<6.6.157.1-1
6.6.157.1-1
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 6.6.157.1-1
Event History
Aug 26, 2026
CVE Published
via MITRE·02:37 PM
Data Sourced
via MITRE·02:37 PM
Description
Data Sourced
via NVD·03:17 PM
Description
Aug 27, 2026
Data Sourced
via Microsoft·08:04 AM
DescriptionSeverityWeaknessAffected Software
Updated
via Microsoft·08:04 AM
DescriptionSeverity
Frequently Asked Questions
1
Does an IPC timeout mean the DSP firmware did not receive the pipeline state-change request?
Not necessarily. The timeout has been root-caused to system scheduling blockage outside the SOF stack; the firmware may have received and handled the message while reply handling was blocked.
2
Why must pipeline state changes continue after a firmware crash?
The kernel must complete its internal state transitions so it can reset its state correctly and work properly when the DSP is booted again.