CVE-2026-90068

ASoC: dapm: Fix off-by-one check on the second enum channel

N/A
Published: September 17, 2026 at 04:05 PM UTC
Updated: October 19, 2026 at 09:18 AM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 0.2%

Description

In the Linux kernel, the following vulnerability has been resolved: ASoC: dapm: Fix off-by-one check on the second enum channel The snd_soc_dapm_put_enum_double() rejects item[0] once it reaches e->items, but it lets item[1] be equal to it. Both go on to snd_soc_enum_item_to_val(), which indexes e->values with no bound of its own, so an enum with a value table reads one element past the end. The indexing arrived with the MUX consolidation, which relaxed the item[1] check in the same hunk. The value MUX handler it deleted used >= there, and the snd_soc_put_enum_double() in soc-ops.c still does. Only adav80x pairs a value table with two shifts, and its second channel looks accidental, but the control does report two values. Writing three into it reads off the end of adav80x_mux_values. The core catches that only under CONFIG_SND_CTL_INPUT_VALIDATION, which defaults off.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

3.153727b4968453dbab8fe18f979d67285eb6b66801
Vendor states this is fixed in 10a36512c21f861a03fba461a7ead09023df9c1b (fixed)
Vendor states this is fixed in 14511c9b54ceeeef487409d73947c89ee8563590 (fixed)
Vendor states this is fixed in 32fc048391112559c34cb88d13594546939a4cd6 (fixed)
Vendor states this is fixed in 496081b4edc1f6e662418831c5b14cddd8d7920c (fixed)
Vendor states this is fixed in 55126ef66298e43c69f192acebae8c7cc0022cf6 (fixed)
Vendor states this is fixed in 57ab955bde747327fb2042516ae1b7192c30e881 (fixed)
Vendor states this is fixed in 806fa4e1f2bf73c54bc4b6360790ecc69d095ca5 (fixed)
Vendor states this is fixed in faf539af1a595a26e5a081a4e512caee2bc2f4c5 (fixed)
Vendor states this is fixed in 3.15 (unaffected)
Vendor states this is fixed in 5.10.270 (unaffected)
Vendor states this is fixed in 5.15.221 (unaffected)
Vendor states this is fixed in 6.1.188 (unaffected)
Vendor states this is fixed in 6.12.110 (unaffected)
Vendor states this is fixed in 6.18.52 (unaffected)
Vendor states this is fixed in 6.6.157 (unaffected)
Vendor states this is fixed in 7.2.6 (unaffected)
Vendor states this is fixed in 7.3 (unaffected)
Vendor states this is fixed in 7.3-rc1 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

Quick Info

StatusRECEIVED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card