From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-80581: ASoC: SOF: ipc4-pcm: Continue the pipeline trigger in case of IPC timeout
Date: Wed, 26 Aug 2026 16:38:17 +0200 [thread overview]
Message-ID: <2026082615-CVE-2026-80581-37a5@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
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.
The Linux kernel CVE team has assigned CVE-2026-80581 to this issue.
Affected and fixed versions
===========================
Issue introduced in 6.8 with commit c40aad7c81e5fba34b70123ed7ce3397fa62a4d2 and fixed in 6.18.46 with commit f2435a46dfa1a5693cf2664afd022db66ee58121
Issue introduced in 6.8 with commit c40aad7c81e5fba34b70123ed7ce3397fa62a4d2 and fixed in 7.1.10 with commit 6b512a5330ef1a41db7aff4b80c4e952b8d52f17
Issue introduced in 6.8 with commit c40aad7c81e5fba34b70123ed7ce3397fa62a4d2 and fixed in 7.2 with commit 17661c67b206612cb3ba65d5ae726cd2015d0a53
Issue introduced in 6.6.23 with commit 3cac6eebea9b4bc5f041e157e45c76e212ad6759
Issue introduced in 6.7.11 with commit d153e8b154f9746ac969c85a4e6474760453647c
Please see https://www.kernel.org for a full list of currently supported
kernel versions by the kernel community.
Unaffected versions might change over time as fixes are backported to
older supported kernel versions. The official CVE entry at
https://cve.org/CVERecord/?id=CVE-2026-80581
will be updated if fixes are backported, please check that for the most
up to date information about this issue.
Affected files
==============
The file(s) affected by this issue are:
sound/soc/sof/ipc4-pcm.c
Mitigation
==========
The Linux kernel CVE team recommends that you update to the latest
stable kernel version for this, and many other bugfixes. Individual
changes are never tested alone, but rather are part of a larger kernel
release. Cherry-picking individual commits is not recommended or
supported by the Linux kernel community at all. If however, updating to
the latest release is impossible, the individual changes to resolve this
issue can be found at these commits:
https://git.kernel.org/stable/c/f2435a46dfa1a5693cf2664afd022db66ee58121
https://git.kernel.org/stable/c/6b512a5330ef1a41db7aff4b80c4e952b8d52f17
https://git.kernel.org/stable/c/17661c67b206612cb3ba65d5ae726cd2015d0a53
reply other threads:[~2026-08-26 14:41 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2026082615-CVE-2026-80581-37a5@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=cve@kernel.org \
--cc=gregkh@kernel.org \
--cc=linux-cve-announce@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.