---
id: CVE-2026-80581
title: 'ASoC: SOF: ipc4-pcm: Continue the pipeline trigger in case of IPC timeout'
summary: |-
  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 t…
severity: none
vendor: Linux
product: Linux
affected:
  - >-
    Linux >= 3cac6eebea9b4bc5f041e157e45c76e212ad6759 <
    4931c09d83877dc350106bae745321c3f295129b
  - >-
    Linux >= c40aad7c81e5fba34b70123ed7ce3397fa62a4d2 <
    96d51b8c5a909937d41f9c03495188d4190f877d
  - >-
    Linux >= c40aad7c81e5fba34b70123ed7ce3397fa62a4d2 <
    f2435a46dfa1a5693cf2664afd022db66ee58121
  - >-
    Linux >= c40aad7c81e5fba34b70123ed7ce3397fa62a4d2 <
    6b512a5330ef1a41db7aff4b80c4e952b8d52f17
  - >-
    Linux >= c40aad7c81e5fba34b70123ed7ce3397fa62a4d2 <
    17661c67b206612cb3ba65d5ae726cd2015d0a53
  - Linux d153e8b154f9746ac969c85a4e6474760453647c
  - Linux >= 6.6.23 < 6.6.154
  - Linux >= 6.7.11 < 6.8
  - Linux 6.8
published: '2026-08-26'
updated: '2026-10-21'
sourceUpdated: '2026-10-21T12:46:31.655Z'
source: CVEORG
sourceUrl: 'https://www.cve.org/CVERecord?id=CVE-2026-80581'
references:
  - url: 'https://git.kernel.org/stable/c/4931c09d83877dc350106bae745321c3f295129b'
  - url: 'https://git.kernel.org/stable/c/96d51b8c5a909937d41f9c03495188d4190f877d'
  - url: 'https://git.kernel.org/stable/c/f2435a46dfa1a5693cf2664afd022db66ee58121'
  - url: 'https://git.kernel.org/stable/c/6b512a5330ef1a41db7aff4b80c4e952b8d52f17'
  - url: 'https://git.kernel.org/stable/c/17661c67b206612cb3ba65d5ae726cd2015d0a53'
tags:
  - cve.org
epss: 0.00209
epssPercentile: 0.10415
ingestedAt: '2026-10-21T12:48:53.573Z'
---

## Overview

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.

## Affected

- `Linux >= 3cac6eebea9b4bc5f041e157e45c76e212ad6759 < 4931c09d83877dc350106bae745321c3f295129b`
- `Linux >= c40aad7c81e5fba34b70123ed7ce3397fa62a4d2 < 96d51b8c5a909937d41f9c03495188d4190f877d`
- `Linux >= c40aad7c81e5fba34b70123ed7ce3397fa62a4d2 < f2435a46dfa1a5693cf2664afd022db66ee58121`
- `Linux >= c40aad7c81e5fba34b70123ed7ce3397fa62a4d2 < 6b512a5330ef1a41db7aff4b80c4e952b8d52f17`
- `Linux >= c40aad7c81e5fba34b70123ed7ce3397fa62a4d2 < 17661c67b206612cb3ba65d5ae726cd2015d0a53`
- `Linux d153e8b154f9746ac969c85a4e6474760453647c`
- `Linux >= 6.6.23 < 6.6.154`
- `Linux >= 6.7.11 < 6.8`
- `Linux 6.8`

## Remediation

Refer to the linked advisories for vendor-supplied fixes and affected version ranges.