From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-43459: ASoC: soc-core: flush delayed work before removing DAIs and widgets
Date: Fri, 8 May 2026 16:23:08 +0200 [thread overview]
Message-ID: <2026050800-CVE-2026-43459-2ed8@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
ASoC: soc-core: flush delayed work before removing DAIs and widgets
When a sound card is unbound while a PCM stream is open, a
use-after-free can occur in snd_soc_dapm_stream_event(), called from
the close_delayed_work workqueue handler.
During unbind, snd_soc_unbind_card() flushes delayed work and then
calls soc_cleanup_card_resources(). Inside cleanup,
snd_card_disconnect_sync() releases all PCM file descriptors, and
the resulting PCM close path can call snd_soc_dapm_stream_stop()
which schedules new delayed work with a pmdown_time timer delay.
Since this happens after the flush in snd_soc_unbind_card(), the
new work is not caught. soc_remove_link_components() then frees
DAPM widgets before this work fires, leading to the use-after-free.
The existing flush in soc_free_pcm_runtime() also cannot help as it
runs after soc_remove_link_components() has already freed the widgets.
Add a flush in soc_cleanup_card_resources() after
snd_card_disconnect_sync() (after which no new PCM closes can
schedule further delayed work) and before soc_remove_link_dais()
and soc_remove_link_components() (which tear down the structures the
delayed work accesses).
The Linux kernel CVE team has assigned CVE-2026-43459 to this issue.
Affected and fixed versions
===========================
Issue introduced in 4.20 with commit e894efef9ac7c10b7727798dcc711cccf07569f9 and fixed in 5.10.253 with commit bf80a89da97285d9b877e0c6995e870d46b8025c
Issue introduced in 4.20 with commit e894efef9ac7c10b7727798dcc711cccf07569f9 and fixed in 5.15.203 with commit 3887e514978d28216246360b46a9cb534969eb5a
Issue introduced in 4.20 with commit e894efef9ac7c10b7727798dcc711cccf07569f9 and fixed in 6.1.167 with commit 231568afbc0cd25b8fb2a94ebf9738eabe1cf007
Issue introduced in 4.20 with commit e894efef9ac7c10b7727798dcc711cccf07569f9 and fixed in 6.6.130 with commit 317a9298c54bb00319da73e5a7179f00e67fcbdf
Issue introduced in 4.20 with commit e894efef9ac7c10b7727798dcc711cccf07569f9 and fixed in 6.12.78 with commit eab71e11ce2447c1e01809cbc11eab4234cf8dc8
Issue introduced in 4.20 with commit e894efef9ac7c10b7727798dcc711cccf07569f9 and fixed in 6.18.19 with commit 7d33e6140945482a07f8089ee86e13e02553ffdb
Issue introduced in 4.20 with commit e894efef9ac7c10b7727798dcc711cccf07569f9 and fixed in 6.19.9 with commit c054f0607c8bb1b1aa529bc109e4149298a1cccd
Issue introduced in 4.20 with commit e894efef9ac7c10b7727798dcc711cccf07569f9 and fixed in 7.0 with commit 95bc5c225513fc3c4ce169563fb5e3929fbb938b
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-43459
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/soc-core.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/bf80a89da97285d9b877e0c6995e870d46b8025c
https://git.kernel.org/stable/c/3887e514978d28216246360b46a9cb534969eb5a
https://git.kernel.org/stable/c/231568afbc0cd25b8fb2a94ebf9738eabe1cf007
https://git.kernel.org/stable/c/317a9298c54bb00319da73e5a7179f00e67fcbdf
https://git.kernel.org/stable/c/eab71e11ce2447c1e01809cbc11eab4234cf8dc8
https://git.kernel.org/stable/c/7d33e6140945482a07f8089ee86e13e02553ffdb
https://git.kernel.org/stable/c/c054f0607c8bb1b1aa529bc109e4149298a1cccd
https://git.kernel.org/stable/c/95bc5c225513fc3c4ce169563fb5e3929fbb938b
reply other threads:[~2026-05-08 14:27 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=2026050800-CVE-2026-43459-2ed8@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox