Bug 2524443 (CVE-2026-80581) - CVE-2026-80581 kernel: ASoC: SOF: ipc4-pcm: Continue the pipeline trigger in case of IPC timeout
Summary: CVE-2026-80581 kernel: ASoC: SOF: ipc4-pcm: Continue the pipeline trigger in ...
Keywords:
Status: NEW
Alias: CVE-2026-80581
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: Product Security
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-08-26 14:54 UTC by OSIDB Bzimport
Modified: 2026-08-27 07:55 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)

Description OSIDB Bzimport 2026-08-26 14:54:57 UTC
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.


Note You need to log in before you can comment on or make changes to this bug.