Look up another CVE · open CVE-2026-53205 in the interactive tracker
CVE-2026-53205
accel/ivpu: Add bounds checks for firmware log indices
Published 2026-06-25 (4 months ago) by the Linux kernel CNA. Subsystem drivers/accel. Debian urgency: unimportant.
What to do, per Debian release
Debian's own status for CVE-2026-53205 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 | 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.13-1 | Update the kernel and reboot. Fixed in 7.0.13-1. A running kernel keeps the old code until the machine restarts. |
| Debian unstablesid | fixed | 7.0.13-1 | Update the kernel and reboot. Fixed in 7.0.13-1. A running kernel keeps the old code until the machine restarts. |
The vulnerability
What the bug is
Add validation that read and write indices in the firmware log buffer are within valid bounds (< data_size) before using them. If out-of-bounds indices are encountered (from firmware), clamp them to safe values instead of proceeding with invalid offsets. This prevents potential out-of-bounds buffer access when firmware supplies invalid log indices.
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.
drivers/accel/ivpu/ivpu_fw_log.c
- What this is
- DRM ACCEL DRIVERS FOR INTEL VPUMAINTAINERS section matched on drivers/accel/ivpu/ · dri-devel@lists.freedesktop.org · Supported
- Kernel module
- intel_vpu
Check it on the machine
grep -wE 'CONFIG_DRM_ACCEL|CONFIG_DRM_ACCEL_IVPU' /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 intel_vpuPrints 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 1 release, so nothing is claimed about those.
- bookworm?
- 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
- ?
- 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_DRM_ACCEL, CONFIG_DRM_ACCEL_IVPU
- 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-06-25 (4 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.12%, higher than 2.0% of all CVEssource
- CISA KEV
- not listedthe KEV catalogue
- Debian urgency
- unimportantsource
- Subsystem
- drivers/accel
Upstream fixes
The versions the CNA records as introducing and fixing this, and the commit for each. source
| Introduced | Fixed in | Commit |
|---|---|---|
| 6.12.30 | 6.12.94 | 5961c7034140 |
| 6.13 | 6.18.36 | 8ec70c0dbdf0 |
| 6.13 | 7.0.13 | 535da9ad8420 |
| 6.13 | 7.1 | dd1311bcf0e6 |
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 vulnerable code is reached through local kernel interfaces for the Intel NPU/ivpu device, including debugfs log reads and recovery/coredump paths after local job submission. There is no network or adjacent-radio entry point.
- AC:LAttack complexity, low
- No race or difficult timing is required once invalid firmware log indices are present; the log read/recovery path directly consumes them. A local attacker can repeatedly exercise the NPU and trigger log printing or recovery.
- PR:LPrivileges required, low
- The relevant DRM accel ioctls do not require capabilities, and the debugfs fw_log file is created as readable when debugfs is accessible. This is reachable by a local low-privileged user with access to the NPU device/debug interface, not by an unauthenticated remote attacker.
- UI:NUser interaction, none
- Exploitation does not require a separate victim action. The attacker can invoke the local device/debugfs path directly.
- S:UScope, unchanged
- The impact is within the local kernel/device driver security authority. It does not cross a VM, IOMMU, or other separate security scope boundary.
- C:HConfidentiality impact, high
- Unbounded firmware-controlled indices can make the driver read far beyond the firmware log BO and print kernel memory through the log/coredump output path. This is an out-of-bounds read that can disclose high-value kernel memory.
- I:NIntegrity impact, none
- The vulnerable path reads bytes and prints them; it does not write out of bounds or provide an evident memory modification primitive. The fix only clamps read offsets.
- A:HAvailability impact, high
- Out-of-bounds reads from a vmapped buffer can fault while walking unmapped memory or consume excessive resources while printing. This can cause a kernel oops/panic or serious denial of service.