From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-80910: ASoC: codecs: lpass-wsa-macro: Fix enum kcontrol accesses
Date: Fri, 4 Sep 2026 19:17:41 +0200 [thread overview]
Message-ID: <2026090435-CVE-2026-80910-46eb@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
ASoC: codecs: lpass-wsa-macro: Fix enum kcontrol accesses
EAR SPKR PA Gain" and the four "WSA RX* Mux" controls are enumerated,
but their get and put callbacks access the value through
ucontrol->value.integer.value[0] (a long) instead of
ucontrol->value.enumerated.item[0] (an unsigned int).
This same pattern was fixed in the sibling drivers by
commit bcfe5f76cc40 ("ASoC: codecs: rx-macro: fix accessing array
out of bounds for enum type") and
commit 0ea5eff7c606 ("ASoC: codecs: va-macro: fix accessing array
out of bounds for enum type"), but wsa-macro was missed.
On 64-bit kernels with CONFIG_SND_CTL_DEBUG this trips the elem value
sanity check and every read of these controls fails with -EINVAL.
The Linux kernel CVE team has assigned CVE-2026-80910 to this issue.
Affected and fixed versions
===========================
Issue introduced in 5.11 with commit 809bcbcecebff86003e13f07444d21b9d6652a64 and fixed in 5.15.217 with commit bd4e5f9c3b764dc0e2a5662f92d63d2f3767a78d
Issue introduced in 5.11 with commit 809bcbcecebff86003e13f07444d21b9d6652a64 and fixed in 6.1.184 with commit 4bcac4bf304a3ec746192e49a669c236aaf27dbf
Issue introduced in 5.11 with commit 809bcbcecebff86003e13f07444d21b9d6652a64 and fixed in 6.6.153 with commit 891129df5de79cd533ae335c6eab24df2ff2b0fd
Issue introduced in 5.11 with commit 809bcbcecebff86003e13f07444d21b9d6652a64 and fixed in 6.12.105 with commit 524aa7b9954b0a43dd13f71ecbbac52a151c326d
Issue introduced in 5.11 with commit 809bcbcecebff86003e13f07444d21b9d6652a64 and fixed in 6.18.46 with commit 2fe7a89b2b5b73be35c1e493d0246314ba54e427
Issue introduced in 5.11 with commit 809bcbcecebff86003e13f07444d21b9d6652a64 and fixed in 7.1.10 with commit 7bcdde412e6c744f6135e02b12a735e2e37b639f
Issue introduced in 5.11 with commit 809bcbcecebff86003e13f07444d21b9d6652a64 and fixed in 7.2 with commit 56f24311fd5607588a47e44675195a9efb200f29
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-80910
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/lpass-wsa-macro.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/bd4e5f9c3b764dc0e2a5662f92d63d2f3767a78d
https://git.kernel.org/stable/c/4bcac4bf304a3ec746192e49a669c236aaf27dbf
https://git.kernel.org/stable/c/891129df5de79cd533ae335c6eab24df2ff2b0fd
https://git.kernel.org/stable/c/524aa7b9954b0a43dd13f71ecbbac52a151c326d
https://git.kernel.org/stable/c/2fe7a89b2b5b73be35c1e493d0246314ba54e427
https://git.kernel.org/stable/c/7bcdde412e6c744f6135e02b12a735e2e37b639f
https://git.kernel.org/stable/c/56f24311fd5607588a47e44675195a9efb200f29
reply other threads:[~2026-09-04 17:21 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=2026090435-CVE-2026-80910-46eb@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.