Look up another CVE · open CVE-2026-64133 in the interactive tracker
CVE-2026-64133
ALSA: asihpi: Fix potential OOB array access at reading cache
Published 2026-07-19 (3 months ago) by the Linux kernel CNA. Subsystem sound/pci. Debian urgency: not yet assigned.
What to do, per Debian release
Debian's own status for CVE-2026-64133 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.176-1 | Update the kernel and reboot. Fixed in 6.1.176-1. A running kernel keeps the old code until the machine restarts. |
| Debian 13trixie | fixed | 6.12.94-1 | Update the kernel and reboot. Fixed in 6.12.94-1. A running kernel keeps the old code until the machine restarts. |
| Debian 14forky | fixed | 7.0.12-1 | Update the kernel and reboot. Fixed in 7.0.12-1. A running kernel keeps the old code until the machine restarts. |
| Debian unstablesid | fixed | 7.0.12-1 | Update the kernel and reboot. Fixed in 7.0.12-1. A running kernel keeps the old code until the machine restarts. |
The vulnerability
What the bug is
find_control() to retrieve a cached info accesses the array with the given index blindly, which may lead to an OOB array access. Add a sanity check for avoiding it.
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/pci/asihpi/hpicmn.c
- What this is
- SOUNDMAINTAINERS section matched on sound/ · linux-sound@vger.kernel.org · Maintained
- Kernel module
- snd_asihpi
Check it on the machine
grep -wE 'CONFIG_SND|CONFIG_SND_ASIHPI' /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_asihpiPrints 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/arm64, arm64/arm64-16k, arm64/cloud-arm64, arm64/rt/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/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
- M
- a module where it is built at all; some flavours do not build it
- Build switches
- CONFIG_SND, CONFIG_SND_ASIHPI
- 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-07-19 (3 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.13%, higher than 2.3% of all CVEssource
- CISA KEV
- not listedthe KEV catalogue
- Debian urgency
- not yet assignedsource
- Subsystem
- sound/pci
Upstream fixes
The versions the CNA records as introducing and fixing this, and the commit for each. source
| Introduced | Fixed in | Commit |
|---|---|---|
| 2.6.35 | 5.10.258 | e060e21fe9cc |
| 2.6.35 | 5.15.209 | 34d0d492a281 |
| 2.6.35 | 6.1.175 | ffa29cea7bf9 |
| 2.6.35 | 6.6.142 | 7b6f8c8eb93f |
| 2.6.35 | 6.12.92 | 8778386e4387 |
| 2.6.35 | 6.18.34 | 61c5017c64e2 |
| 2.6.35 | 7.0.11 | 7d1072399357 |
| 2.6.35 | 7.1 | 7b7d6572145c |
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 local ALSA hwdep ioctl (`HPI_IOCTL_LINUX` on `/dev/snd/hwC*D0`) or equivalent in-kernel `hpi_send_recv()` calls; there is no network, Bluetooth, or physical-device attack surface for this PCI audio driver path.
- AC:LAttack complexity, low
- On systems with an AudioScience adapter and control cache enabled, an attacker fully controls `obj_index` in the HPI control message and can reliably trigger the out-of-bounds access with a single crafted ioctl without races or victim-dependent timing.
- PR:LPrivileges required, low
- Exploitation requires only local access to the ALSA sound/hwdep device nodes (typically any unprivileged user in the `audio` group), not real root or capabilities that cannot be obtained through user namespaces.
- UI:NUser interaction, none
- No victim interaction is required; the attacker opens the hwdep device and issues crafted HPI control messages directly without needing another user to perform any action.
- S:UScope, unchanged
- Impact is confined to kernel memory within the same security authority (local privilege escalation / kernel crash); it does not cross VM, IOMMU, or sandbox boundaries.
- C:HConfidentiality impact, high
- The out-of-bounds read of `p_cache->p_info[control_index]` returns adjacent kernel heap pointers/data, and `hpi_check_control_cache_single()` dereferences the corrupted pointer and copies interpreted fields into the ioctl response buffer, enabling kernel information disclosure.
- I:HIntegrity impact, high
- After the out-of-bounds pointer load, follow-on cache handling dereferences attacker-influenced kernel addresses for reads and, on SET_STATE or PAD control paths, performs writes (e.g., null-termination), providing exploitable kernel memory corruption beyond a simple crash.
- A:HAvailability impact, high
- A large out-of-bounds `obj_index` can read unmapped memory and cause a kernel oops/panic, and invalid pointer dereferences in the cache-handling path can crash or hang the system.