CVE-2026-80581

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

Published Aug 26, 2026 CVSS 3.1 · 5.5 Medium EPSS < 1% KEV · Not listed
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.

Analysis

AI-generated

Technical impact

A bug in the Linux kernel’s ASoC SOF audio stack allowed the kernel to ignore failures from IPC time‑outs or firmware crashes and continue resetting the audio pipeline state incorrectly. The lack of proper error handling could leave the audio subsystem in an inconsistent or unusable state, potentially resulting in audio failures or kernel instability if the pipeline reset never completes.

Affected Systems

All Linux kernel builds that include the ASoC SOF ipc4‑pcm driver without the commit referenced in the advisory are potentially affected. The advisory does not list specific version numbers, so any kernel that implements the unpatched logic prior to the fix is considered at risk.

Risk and Exploitability

The CVSS score is 5.5, and the EPSS score is < 1%, indicating that the exploitation probability is low. The vulnerability is listed as not in the CISA KEV catalog. The most likely attack vector is local; an attacker would need to induce a firmware crash or create a scheduling blockage that triggers an IPC timeout. Because the conditions for exploitation are specific and not easily controllable remotely, the risk of exploitation is low at present.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Apply a kernel update that includes the commit at https://git.kernel.org/stable/c/17661c67b206612cb3ba65d5ae726cd2015d0a53
  • Reboot the system to load the updated driver and verify that audio functionality is restored
  • If a kernel update cannot be applied immediately, minimize CPU‑bound workloads or scheduling constraints that could block IRQ handling, as this is a temporary mitigation against IPC timeouts.

Generated by OpenCVE AI on August 28, 2026 at 17:26 UTC.

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
Debian DLA Debian DLA DLA-4904-1 linux-6.12 security update
Ubuntu USN Ubuntu USN USN-9019-1 Linux kernel (Azure) vulnerabilities
Ubuntu USN Ubuntu USN USN-9020-1 Linux kernel vulnerabilities
Ubuntu USN Ubuntu USN USN-9022-1 Linux kernel vulnerabilities
Ubuntu USN Ubuntu USN USN-9023-1 Linux kernel vulnerabilities
Ubuntu USN Ubuntu USN USN-9024-1 Linux kernel vulnerabilities
Ubuntu USN Ubuntu USN USN-9025-1 Linux kernel vulnerabilities
Ubuntu USN Ubuntu USN USN-9026-1 Linux kernel (Azure) vulnerabilities
Ubuntu USN Ubuntu USN USN-9039-1 Linux kernel (Azure CVM) vulnerabilities
Ubuntu USN Ubuntu USN USN-9040-1 Linux kernel (Low Latency NVIDIA) vulnerabilities
Ubuntu USN Ubuntu USN USN-9066-1 Linux kernel (HWE) vulnerabilities
Ubuntu USN Ubuntu USN USN-9091-1 Linux kernel (NVIDIA Tegra) vulnerabilities
History
Type Values Removed Values Added
Weaknesses CWE-703
Type Values Removed Values Added
Weaknesses CWE-390
References
Metrics threat_severity

None

cvssV3_1

{'score': 5.5, 'vector': 'CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H'}

threat_severity

Low

Type Values Removed Values Added
Weaknesses CWE-703
Type Values Removed Values Added
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.
Title ASoC: SOF: ipc4-pcm: Continue the pipeline trigger in case of IPC timeout
First Time appeared Linux
Linux linux Kernel
CPEs cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
Vendors & Products Linux
Linux linux Kernel
References
Weaknesses
  • CWE-390

    Detection of Error Condition Without Action

Sources

Status
PUBLISHED
Assigner
Linux
Published
Updated
Oct 30, 2026, 12:30 PM
Reserved
Aug 26, 2026, 2:34 PM
Status
Received
Published
Aug 26, 2026, 3:17 PM
Modified
Oct 30, 2026, 1:20 PM
Severity
Low
Public date
Aug 26, 2026, 12:00 AM