Look up another CVE · open CVE-2026-72089 in the interactive tracker
CVE-2026-72089
accel/ivpu: Reject firmware log with size smaller than header
Published 2026-08-15 (2 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-72089 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.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
fw_log_from_bo() validates the tracing buffer header_size and that the log fits within the BO, but never checks that log->size is at least log->header_size. fw_log_print_buffer() then computes: u32 data_size = log->size - log->header_size; which underflows to a near-U32_MAX value when firmware reports a log whose size is smaller than its header. That huge data_size defeats the log_start/log_end bounds clamps added by commit dd1311bcf0e6 ("accel/ivpu: Add bounds checks for firmware log indices"), so fw_log_print_lines() reads far past the small real data region of the BO. A size of 0 also makes fw_log_from_bo() advance the offset by 0, causing the callers to loop forever on the same header. Reject logs whose size is smaller than the header (which also rejects size == 0).
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-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.4% 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.6 | 6.6.148 | 5592a207e158 |
| 6.6 | 6.12.97 | dc9a1cda2e46 |
| 6.6 | 6.18.40 | 257321a1c036 |
| 6.6 | 7.1.5 | 6920e62be4c9 |
| 6.6 | 7.2 | ddb44baed257 |
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 in Intel NPU (ivpu) firmware log parsing reached only via local debugfs reads/writes or automatic driver recovery/coredump paths after submitting work through the DRM render node; there is no network-facing entry point.
- AC:LAttack complexity, low
- An unprivileged local user can repeatedly submit NPU jobs to provoke firmware faults/timeouts that leave malformed tracing headers and then reliably trigger kernel log parsing during recovery, coredump, or fw_log access without depending on uncontrollable timing or layout.
- PR:LPrivileges required, low
- Exploitation requires only standard local access to the Intel NPU DRM render node to submit inference jobs and provoke recovery; it does not require root/CAP_SYS_ADMIN, and the device is not reachable from unprivileged user namespaces.
- UI:NUser interaction, none
- No victim interaction is required; the attacker triggers malformed firmware log processing themselves via job submission and the resulting automatic recovery/coredump path or by reading debugfs fw_log.
- S:UScope, unchanged
- Impact is confined to kernel memory and availability on the same host running the ivpu driver; it does not cross VM, container, or IOMMU security boundaries.
- C:HConfidentiality impact, high
- Integer underflow makes data_size wrap to ~U32_MAX, bypassing index clamps so fw_log_print_lines performs a massive out-of-bounds read past the tracing BO and can disclose adjacent kernel memory via drm_printf/coredump output.
- I:NIntegrity impact, none
- The flaw is an out-of-bounds read and possible infinite loop during parsing; it does not provide an arbitrary kernel write, code execution, or other integrity-modifying primitive.
- A:HAvailability impact, high
- A near-U32_MAX read can oops/panic the kernel when accessing unmapped memory, and log size 0 prevents offset advancement causing an infinite loop in fw_log_print_all_in_bo during coredump, reset, or debugfs access, hanging the system.