Look up another CVE · open CVE-2026-72415 in the interactive tracker
CVE-2026-72415
ASoC: SDCA: Validate written enum value in ge_put_enum_double()
Published 2026-08-15 (2 months ago) by the Linux kernel CNA. Subsystem sound/soc. Debian urgency: unimportant.
What to do, per Debian release
Debian's own status for CVE-2026-72415 in every release this site tracks, and what each one means in practice. Every status below is the one the Debian Security Team publishes for this CVE. source
| Release | Status | Version | What this means |
|---|---|---|---|
| Debian 12bookworm | not affected | 6.1.190-1 | Nothing to do. bookworm never shipped the vulnerable code. |
| Debian 13trixie | not affected | 6.12.113-1 | Nothing to do. trixie never shipped the vulnerable code. |
| Debian 14forky | fixed | 7.1.5-1 | Update the kernel and reboot. Fixed in 7.1.5-1. A running kernel keeps the old code until the machine restarts. |
| Debian unstablesid | fixed | 7.1.5-1 | Update the kernel and reboot. Fixed in 7.1.5-1. A running kernel keeps the old code until the machine restarts. |
The vulnerability
What the bug is
ge_put_enum_double() passes the user-supplied enumeration index item[0] to snd_soc_enum_item_to_val() without checking it against the number of items in the enum: ret = snd_soc_enum_item_to_val(e, item[0]); snd_soc_enum_item_to_val() indexes the heap-allocated e->values[] array with that index (e->values is set from a devm_kcalloc() of e->items entries), so a control write with an out-of-range item[0] reads past the end of the values buffer. The bounds check in snd_soc_dapm_put_enum_double() only runs afterwards, so it does not prevent the read here. Reject an out-of-range item before using it, matching the other enum put handlers. This issue was pointed out by the Sashiko AI review bot while reviewing a related enum-validation series: https://lore.kernel.org/all/20260609125735.CEB651F00893@smtp.kernel.org/
Where it lives
The fix touches these files. If the subsystem is one you do not use, the practical exposure is lower, though the package is still the vulnerable one.
sound/soc/sdca/sdca_asoc.c
- What this is
- SDCA LIBRARY AND CLASS DRIVERMAINTAINERS section matched on sound/soc/sdca/* · linux-sound@vger.kernel.org · Maintained
- Kernel module
- snd_soc_sdca
Check it on the machine
grep -wE 'CONFIG_SND|CONFIG_SND_SOC|CONFIG_SND_SOC_SDCA' /boot/config-$(uname -r)Reads the booted kernel's own configuration, on the machine and nowhere else. =y is built in, =m is a module, and an is not set line means the code is not there.
lsmod | grep -w snd_soc_sdcaPrints a line if that module is loaded right now, and nothing if it is not. One that is not loaded can still be loaded later by anything that needs it.
Show whether Debian builds this, per release
Debian builds this, but not on every flavour. At least one release below builds the code on some of its kernel flavours and not on others, so the answer depends on the architecture and flavour installed. The build rule could not be established for 2 releases, so nothing is claimed about those.
- bookworm, trixie?
- forky, sidMnot built on amd64/cloud-amd64, arm64/arm64, arm64/arm64-16k, arm64/cloud-arm64, arm64/rt-arm64, armhf/armmp, armhf/armmp-lpae, loong64/loong64, ppc64el/powerpc64le, ppc64el/powerpc64le-64k, riscv64/riscv64, s390x/s390x
- ?
- not established - no Makefile entry for the affected file
- M
- a module where it is built at all; some flavours do not build it
Where a release above reads "not established", no build rule for the affected file was found in that release's kernel tree. That is a gap in this lookup, not a finding that the code is absent.
- Build switches
- CONFIG_SND, CONFIG_SND_SOC, CONFIG_SND_SOC_SDCA
- Reads as
- all on means the file is compiled; any one off means it is not.
From the configuration Debian publishes for every kernel flavour it builds. It covers only the architectures Debian ships a linux-config package for, and nothing about a kernel you built yourself. Debian's own status above stays authoritative about the source package.MAINTAINERS kbuild Makefiles Debian linux-config packages
Signals
- Published
- 2026-08-15 (2 months ago)source
- CVSS
- 7.1 high
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:Hsource recompute it - Attack vector
- local (AV:L)source
- EPSS
- 0.16%, higher than 4.3% of all CVEssource
- CISA KEV
- not listedthe KEV catalogue
- Debian urgency
- unimportantsource
- Subsystem
- sound/soc
Upstream fixes
The versions the CNA records as introducing and fixing this, and the commit for each. source
| Introduced | Fixed in | Commit |
|---|---|---|
| 7.0 | 7.1.5 | 33387bf9bb61 |
| 7.0 | 7.2 | 1ce42a11bed1 |
Why the CNA scored it this way
Quoted from the kernel CNA's own scoring file, word for word. A highlighted metric carries the most severe value CVSS v3.1 defines for it, which is what pushes the score up. source
- AV:LAttack vector, local
- The flaw is reached only via a local ALSA mixer control write (SNDRV_CTL_IOCTL_ELEM_WRITE on /dev/snd/controlC*) to the SDCA Group Entity "Selected Mode" enum exposed by ge_put_enum_double(); there is no network, Bluetooth, or physical-bus packet path to this handler.
- AC:LAttack complexity, low
- An attacker can reliably issue a control write with an out-of-range enumerated index; the only extra condition is detected jack mode >2, which is satisfied by plugging a headset into the affected laptop's audio jack on typical SDCA-equipped systems.
- PR:LPrivileges required, low
- Exploitation requires only local access to the ALSA control device, which on standard desktop and laptop distributions is available to unprivileged users in the audio group without CAP_SYS_ADMIN or init-namespace root.
- UI:NUser interaction, none
- No action by a separate victim is required; the attacker triggers the vulnerable put handler directly through their own ioctl or mixer-tool write to the affected control.
- S:UScope, unchanged
- The out-of-bounds read corrupts kernel heap metadata or leaks adjacent kernel memory within the same kernel security boundary; it does not by itself cross VM, container, or IOMMU isolation boundaries.
- C:HConfidentiality impact, high
- snd_soc_enum_item_to_val() indexes the heap-allocated e->values[] array with attacker-controlled item[0] before any bounds check, enabling an out-of-bounds kernel heap read that can disclose adjacent sensitive kernel memory contents.
- I:NIntegrity impact, none
- The defect is an out-of-bounds read only; snd_soc_dapm_put_enum_double() still rejects invalid indices before any register write, so the bug does not directly modify kernel memory or achieve arbitrary write or code execution.
- A:HAvailability impact, high
- A sufficiently large out-of-range enum index can read far beyond the small devm_kcalloc()-allocated values buffer and fault on unmapped kernel memory, causing a kernel oops or panic and denial of service on affected SDCA audio systems.