Look up another CVE · open CVE-2026-74295 in the interactive tracker
CVE-2026-74295
ASoC: codecs: hdac_hdmi: Validate written enum value
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-74295 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
hdac_hdmi_set_pin_port_mux() uses the written enum value to index the texts array before calling snd_soc_dapm_put_enum_double(), which validates that the value is within the enum item range. An out-of-range value can therefore make the driver read past the texts array before the helper rejects the write. Move the lookup after the helper has accepted the value.
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/codecs/hdac_hdmi.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
- snd_soc_hdac_hdmi
Check it on the machine
grep -wE 'CONFIG_SND|CONFIG_SND_SOC|CONFIG_SND_SOC_HDAC_HDMI' /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_hdac_hdmiPrints 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 does not build this code in 3 releases. It does build it in 1 release, so the answer depends on which release the machine runs.
- bookwormMnot built on amd64/cloud-amd64, arm64/arm64, arm64/cloud-arm64, arm64/rt/arm64, armhf/armmp, armhf/armmp-lpae, armhf/rt/armmp, ppc64el/powerpc64le
- trixie, forky, sidn
- M
- a module where it is built at all; some flavours do not build it
- n
- not enabled on any flavour - this release does not build the code
- Build switches
- CONFIG_SND, CONFIG_SND_SOC, CONFIG_SND_SOC_HDAC_HDMI
- 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 |
|---|---|---|
| 4.6 | 5.15.212 | 216336418c00 |
| 4.6 | 6.1.178 | bc464a6a9e35 |
| 4.6 | 6.6.145 | 8cbf24714d6b |
| 4.6 | 6.12.97 | 7f02e9064b6f |
| 4.6 | 6.18.40 | 9131e4b023e0 |
| 4.6 | 7.1.5 | d8961b5c7889 |
| 4.6 | 7.2 | 0b08baeccdcf |
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 through local ALSA control ioctls on /dev/snd/controlC* (SNDRV_CTL_IOCTL_ELEM_WRITE), which invoke hdac_hdmi_set_pin_port_mux(); there is no network, Bluetooth, or physical-input path to this callback.
- AC:LAttack complexity, low
- An attacker with access to the ALSA control device can supply any out-of-range enumerated.item[0] value and reliably trigger the out-of-bounds texts[] read on default kernels without CONFIG_SND_CTL_INPUT_VALIDATION, without races or other uncontrollable conditions.
- PR:LPrivileges required, low
- Exploitation requires local access to the ALSA control device (/dev/snd/controlC*), typically granted to the logged-in desktop user or audio group; no CAP_SYS_ADMIN or real root is required and user namespaces do not gate this path.
- UI:NUser interaction, none
- Once the attacker has ALSA control-device access, they can issue the ioctl directly to the Pin port Input mux control without requiring any action from another user or victim.
- S:UScope, unchanged
- The vulnerable Intel HDMI/DP audio codec driver and resulting kernel memory impacts remain within the host kernel security authority and do not cross VM, container, or IOMMU security boundaries.
- C:HConfidentiality impact, high
- The unchecked enum index performs an out-of-bounds read of e->texts[], loading attacker-chosen adjacent kernel heap memory as a char* before validation rejects the write; per conservative kernel guidance, out-of-bounds reads are scored High.
- I:NIntegrity impact, none
- The bug is a read-only out-of-bounds array access with no out-of-bounds write, heap corruption, or attacker-controlled modification; snd_soc_dapm_put_enum_double() rejects invalid values before persisting any mux state change.
- A:HAvailability impact, high
- Attacker-controlled out-of-bounds indices can load texts[] from unmapped addresses and fault the kernel during the pointer fetch; even near-boundary reads are a memory-safety violation treated conservatively as potential denial-of-service on affected Intel HDMI systems.