Look up another CVE · open CVE-2026-72302 in the interactive tracker
CVE-2026-72302
ASoC: SOF: ipc3-control: Use overflow checks in control_update size calc
Published 2026-08-15 (2 months ago) by the Linux kernel CNA. Subsystem sound/soc. Debian urgency: not yet assigned.
What to do, per Debian release
Debian's own status for CVE-2026-72302 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 | fixed | 6.1.180-1 | Update the kernel and reboot. Fixed in 6.1.180-1. A running kernel keeps the old code until the machine restarts. |
| Debian 13trixie | fixed | 6.12.100-1 | Update the kernel and reboot. Fixed in 6.12.100-1. A running kernel keeps the old code until the machine restarts. |
| 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
In sof_ipc3_control_update(), the expected_size calculation uses firmware-provided cdata->num_elems in arithmetic that could overflow on 32-bit platforms, wrapping to a small value. This would allow the cdata->rhdr.hdr.size comparison to pass with mismatched sizes, potentially leading to out-of-bounds access in snd_sof_update_control. Use check_mul_overflow() and check_add_overflow() to detect and reject overflowed size calculations.
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/sof/ipc3-control.c
- What this is
- SOUND - SOUND OPEN FIRMWARE (SOF) DRIVERSMAINTAINERS section matched on sound/soc/sof/ · sound-open-firmware@alsa-project.org · Supported
- Kernel module
- snd_sof
Check it on the machine
grep -wE 'CONFIG_SND|CONFIG_SND_SOC|CONFIG_SND_SOC_SOF' /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_sofPrints 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.
- bookwormMnot built on amd64/cloud-amd64, arm64/arm64, arm64/cloud-arm64, arm64/rt/arm64, armhf/armmp, armhf/armmp-lpae, armhf/rt/armmp, ppc64el/powerpc64le
- trixieMnot built on amd64/cloud-amd64, arm64/cloud-arm64, armel/rpi, armhf/armmp, armhf/armmp-lpae, armhf/rt/armmp, ppc64el/powerpc64le, ppc64el/powerpc64le-64k, riscv64/riscv64, s390x/s390x
- forky, sidMnot built on amd64/cloud-amd64, arm64/cloud-arm64, armhf/armmp, armhf/armmp-lpae, loong64/loong64, ppc64el/powerpc64le, ppc64el/powerpc64le-64k, riscv64/riscv64, s390x/s390x
- M
- a module where it is built at all; some flavours do not build it
- Build switches
- CONFIG_SND, CONFIG_SND_SOC, CONFIG_SND_SOC_SOF
- 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.8 high
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:Hsource recompute it - Attack vector
- local (AV:L)source
- EPSS
- 0.18%, higher than 6.8% of all CVEssource
- CISA KEV
- not listedthe KEV catalogue
- Debian urgency
- not yet assignedsource
- 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 |
|---|---|---|
| 5.18 | 6.1.178 | 6856b3c23b09 |
| 5.18 | 6.6.145 | 89a2309a9eec |
| 5.18 | 6.12.97 | ffd79e77f2fb |
| 5.18 | 6.18.40 | 711d912b1876 |
| 5.18 | 7.1.5 | 312c7d2ebe69 |
| 5.18 | 7.2 | 8791977d7289 |
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 when the on-chip SOF DSP delivers IPC3 GET_VALUE/GET_DATA component notifications via mailbox IRQ into sof_ipc3_control_update(); this requires local access to SOF-equipped audio hardware, not remote network delivery.
- AC:LAttack complexity, low
- On affected 32-bit builds, firmware-supplied num_elems deterministically wraps expected_size so the hdr.size check passes; a local attacker can repeatedly drive DSP control notifications through ALSA without uncontrollable races or victim-specific state.
- PR:LPrivileges required, low
- Only an unprivileged local user able to open ALSA control devices on SOF IPC3 hardware (typical audio-group access on laptops, Chromebooks, and 32-bit embedded tablets) is needed to exercise DSP control paths that deliver the malformed IPC payloads.
- UI:NUser interaction, none
- No separate victim interaction is required; the attacker triggers SOF control-update handling through their own ALSA audio/control activity and the kernel processes the malformed IPC notification automatically.
- S:UScope, unchanged
- Heap corruption and control-cache overread/overwrite remain within the host kernel audio driver on the same machine and do not cross VM, container, or IOMMU boundaries into another security authority.
- C:HConfidentiality impact, high
- Bypassed size validation lets snd_sof_update_control() read chanv/binary data past the kmalloc IPC buffer via loops or memcpy, yielding out-of-bounds kernel heap reads that can disclose adjacent memory contents.
- I:HIntegrity impact, high
- Crafted num_elems drives out-of-bounds copying from the IPC message into control caches, corrupting kernel heap objects and enabling attacker-influenced writes exploitable for further privilege escalation.
- A:HAvailability impact, high
- Out-of-bounds accesses during IRQ-threaded IPC3 control-update handling can cause KASAN faults, unhandled page faults, kernel oops, or panic under realistic SOF audio workloads on 32-bit systems.