From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-53350: ASoC: wm_adsp: Fix NULL dereference when removing firmware controls
Date: Wed, 1 Jul 2026 15:35:05 +0200 [thread overview]
Message-ID: <2026070146-CVE-2026-53350-dcd9@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
ASoC: wm_adsp: Fix NULL dereference when removing firmware controls
In wm_adsp_control_remove() check that the priv pointer is not NULL
before attempting to cleanup what it points to.
When cs_dsp creates a control it calls wm_adsp_control_add_cb() so that
wm_adsp can create its own private control data. There are two cases
where private data is not created:
1. The control is a SYSTEM control, so an ALSA control is not created.
2. The codec driver has registered a control_add() callback that
hides the control, so wm_adsp_control_add() is not called.
When cs_dsp_remove destroys its control list it calls
wm_adsp_control_remove() for each control. But wm_adsp_control_remove()
was attempting to cleanup the private data pointed to by cs_ctl->priv
without checking the pointer for NULL.
The Linux kernel CVE team has assigned CVE-2026-53350 to this issue.
Affected and fixed versions
===========================
Issue introduced in 5.16 with commit 0700bc2fb94c28459f57a10d2ee2c7ef4cb70862 and fixed in 6.1.176 with commit 5ee9bbe2af2f373e08d3017f9aef2f2eaf29fbc3
Issue introduced in 5.16 with commit 0700bc2fb94c28459f57a10d2ee2c7ef4cb70862 and fixed in 6.6.143 with commit 10def23b67b42679d5b1a356e1a6f3498bd188c3
Issue introduced in 5.16 with commit 0700bc2fb94c28459f57a10d2ee2c7ef4cb70862 and fixed in 6.12.94 with commit 2f1be283aa777d655525d000d16474b7e7d015ea
Issue introduced in 5.16 with commit 0700bc2fb94c28459f57a10d2ee2c7ef4cb70862 and fixed in 6.18.36 with commit 12e579b889624ec54a201d98fdff975de556c731
Issue introduced in 5.16 with commit 0700bc2fb94c28459f57a10d2ee2c7ef4cb70862 and fixed in 7.0.13 with commit 6effd6f7b0ba1f5d1df702b2ef7460bcc215e9b7
Issue introduced in 5.16 with commit 0700bc2fb94c28459f57a10d2ee2c7ef4cb70862 and fixed in 7.1 with commit 7d3fb78b550301e43fdc60312aed733069694426
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-53350
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/codecs/wm_adsp.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/5ee9bbe2af2f373e08d3017f9aef2f2eaf29fbc3
https://git.kernel.org/stable/c/10def23b67b42679d5b1a356e1a6f3498bd188c3
https://git.kernel.org/stable/c/2f1be283aa777d655525d000d16474b7e7d015ea
https://git.kernel.org/stable/c/12e579b889624ec54a201d98fdff975de556c731
https://git.kernel.org/stable/c/6effd6f7b0ba1f5d1df702b2ef7460bcc215e9b7
https://git.kernel.org/stable/c/7d3fb78b550301e43fdc60312aed733069694426
reply other threads:[~2026-07-01 13:35 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=2026070146-CVE-2026-53350-dcd9@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.