Look up another CVE · open CVE-2026-74292 in the interactive tracker
CVE-2026-74292
ASoC: tegra: tegra210_ahub: Validate written enum value
Published 2026-08-15 (2 months ago) by the Linux kernel CNA. Subsystem sound/soc. Debian urgency: not yet assigned.
Debian does not build this code. The per-release build detail is under "Where it lives" below.
What to do, per Debian release
Debian's own status for CVE-2026-74292 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
tegra_ahub_put_value_enum() reads e->values[item[0]] before checking whether item[0] is within the enum item range. The existing check therefore happens too late to prevent an out-of-range read of the values array. Move the check before the array access.
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/tegra/tegra210_ahub.c
- What this is
- SOUND - SOC LAYER / DYNAMIC AUDIO POWER MANAGEMENT (ASoC)MAINTAINERS section matched on sound/soc/ · linux-sound@vger.kernel.org · Supported
- Kernel module
- none to look for. The file would have gone into snd_soc_tegra210_ahub, and Debian does not compile it into that module, so finding snd_soc_tegra210_ahub in lsmod would say nothing about this CVE.
Check it on the machine
grep -wE 'CONFIG_SND|CONFIG_SND_SOC|CONFIG_SND_SOC_TEGRA210_AHUB' /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.
Show whether Debian builds this, per release
Debian does not build this code. In 4 releases below, every kernel flavour Debian publishes has the switch off, so the vulnerable file is compiled into no kernel binary Debian ships.
- bookworm, trixie, forky, sidn
- n
- not enabled on any flavour - this release does not build the code
- Build switches
- CONFIG_SND, CONFIG_SND_SOC, CONFIG_SND_SOC_TEGRA210_AHUB
- 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.17%, higher than 5.5% 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.9 | 5.10.261 | 4e45e4c20155 |
| 5.9 | 5.15.212 | 964f8f9015fb |
| 5.9 | 6.1.178 | 2ec7d16fe21c |
| 5.9 | 6.6.145 | 4bcb23635d50 |
| 5.9 | 6.12.97 | f67d63628fe1 |
| 5.9 | 6.18.40 | e098c9c6477d |
| 5.9 | 7.1.5 | 226d93b65f4f |
| 5.9 | 7.2 | 1d8aabb413b5 |
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 bug is reached only via a local ALSA control write (ioctl on /dev/snd/controlC*) to a tegra210_ahub DAPM mux Route enum; there is no network, Bluetooth, or physical-bus path to this callback on Tegra AHUB platforms.
- AC:LAttack complexity, low
- An attacker with access to the ALSA control device can set enumerated.item[0] above e->items and reliably trigger the out-of-bounds read on every attempt; no race, special timing, or victim state is required beyond the driver being loaded.
- PR:LPrivileges required, low
- Exploitation requires only local ability to open and write ALSA mixer controls, which on typical Linux/Tegra deployments (Jetson, automotive IVI, embedded kiosks) is granted to standard users in the audio group rather than requiring init-namespace root.
- UI:NUser interaction, none
- No end-user action such as plugging in hardware or mounting media is needed; a local attacker directly issues the crafted control write to trigger tegra_ahub_put_value_enum().
- S:UScope, unchanged
- Impact is confined to kernel memory disclosure or denial-of-service within the same OS security boundary; this is not a VM escape, IOMMU bypass, or cross-authority sandbox breakout.
- C:HConfidentiality impact, high
- tegra_ahub_put_value_enum() indexes e->values[item[0]] before validating item[0] < e->items, giving an attacker-controlled out-of-bounds kernel read that can disclose adjacent memory and, with large indices, probe arbitrary offsets.
- I:NIntegrity impact, none
- When item[0] is out of range the function returns -EINVAL before using the fetched value to compute reg_idx/bit_pos or update AHUB crossbar registers, so the flaw does not directly modify kernel memory or hardware state.
- A:HAvailability impact, high
- Supplying a sufficiently large out-of-bounds item[0] can read unmapped kernel memory and trigger a kernel oops or panic; even bounded over-reads enable repeatable local denial-of-service against audio-critical Tegra systems.