From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-43480: ASoC: amd: acp3x-rt5682-max9836: Add missing error check for clock acquisition
Date: Wed, 13 May 2026 17:08:48 +0200 [thread overview]
Message-ID: <2026051348-CVE-2026-43480-da19@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
ASoC: amd: acp3x-rt5682-max9836: Add missing error check for clock acquisition
The acp3x_5682_init() function did not check the return value of
clk_get(), which could lead to dereferencing error pointers in
rt5682_clk_enable().
Fix this by:
1. Changing clk_get() to the device-managed devm_clk_get().
2. Adding proper IS_ERR() checks for both clock acquisitions.
The Linux kernel CVE team has assigned CVE-2026-43480 to this issue.
Affected and fixed versions
===========================
Issue introduced in 5.7 with commit 6b8e4e7db3cd236a2cbb720360fb135087a2ac1d and fixed in 5.10.253 with commit 2dc43ac8da7b2bebc5a51a3d86a6275d78f27cff
Issue introduced in 5.7 with commit 6b8e4e7db3cd236a2cbb720360fb135087a2ac1d and fixed in 5.15.203 with commit 4d802f23fcbfec05134653fd001f6c7c3fd55196
Issue introduced in 5.7 with commit 6b8e4e7db3cd236a2cbb720360fb135087a2ac1d and fixed in 6.1.167 with commit 2b0c4a399c8d27f20ecf17dda76751141d6dbb59
Issue introduced in 5.7 with commit 6b8e4e7db3cd236a2cbb720360fb135087a2ac1d and fixed in 6.6.130 with commit 35c7624d30cb45ec336cd16ce072acc32ae351cb
Issue introduced in 5.7 with commit 6b8e4e7db3cd236a2cbb720360fb135087a2ac1d and fixed in 6.12.78 with commit 33de168afdd57265a0e0c20dbd3648a2d8f7cdc4
Issue introduced in 5.7 with commit 6b8e4e7db3cd236a2cbb720360fb135087a2ac1d and fixed in 6.18.19 with commit 790851ecc983c719fa2e6adb17b02f3acc1d217d
Issue introduced in 5.7 with commit 6b8e4e7db3cd236a2cbb720360fb135087a2ac1d and fixed in 6.19.9 with commit 092522621901b5e6af61db04a53f5b313903c6d0
Issue introduced in 5.7 with commit 6b8e4e7db3cd236a2cbb720360fb135087a2ac1d and fixed in 7.0 with commit 53f3a900e9a383d47af7253076e19f510c5708d0
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-43480
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/amd/acp3x-rt5682-max9836.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/2dc43ac8da7b2bebc5a51a3d86a6275d78f27cff
https://git.kernel.org/stable/c/4d802f23fcbfec05134653fd001f6c7c3fd55196
https://git.kernel.org/stable/c/2b0c4a399c8d27f20ecf17dda76751141d6dbb59
https://git.kernel.org/stable/c/35c7624d30cb45ec336cd16ce072acc32ae351cb
https://git.kernel.org/stable/c/33de168afdd57265a0e0c20dbd3648a2d8f7cdc4
https://git.kernel.org/stable/c/790851ecc983c719fa2e6adb17b02f3acc1d217d
https://git.kernel.org/stable/c/092522621901b5e6af61db04a53f5b313903c6d0
https://git.kernel.org/stable/c/53f3a900e9a383d47af7253076e19f510c5708d0
reply other threads:[~2026-05-13 15:09 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=2026051348-CVE-2026-43480-da19@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