Look up another CVE · open CVE-2026-53202 in the interactive tracker
CVE-2026-53202
accel/ivpu: Fix signed integer truncation in IPC receive
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-53202 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
Fix potential buffer overflow where firmware-supplied data_size is cast to signed int before being used in min_t(). Large unsigned values (>= 0x80000000) become negative, causing unsigned wraparound and oversized memcpy operations that can overflow the stack buffer. Change min_t(int, ...) to min() as both values are unsigned and can be handled by min() without explicit cast.
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_ipc.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.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.16%, higher than 4.3% 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.8 | 6.12.94 | 4788556d4dd9 |
| 6.8 | 6.18.36 | 45cb105b8642 |
| 6.8 | 7.0.13 | 2821bf2b79e4 |
| 6.8 | 7.1 | d9faef564438 |
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 IPC receive path is reached through local DRM/accel device operations and driver-triggered JSM IPC responses, not through network or adjacent protocols.
- AC:LAttack complexity, low
- Triggering the vulnerable copy requires a malformed firmware IPC response with a large data_size, but there is no race or external timing condition once such a response is induced; when uncertain, the lower complexity is chosen.
- PR:LPrivileges required, low
- The ivpu accel ioctls require local access to the accelerator device file but no CAP_SYS_ADMIN, DRM master, or other kernel capability checks were found on the relevant paths.
- UI:NUser interaction, none
- The attacker can open the device and issue ioctls or submit work directly; no separate victim action is required.
- S:UScope, unchanged
- The corruption affects the kernel driver/host kernel within the same security authority and does not by itself cross a VM, sandbox, or IOMMU security boundary.
- C:HConfidentiality impact, high
- The signed truncation can turn firmware-controlled data_size into an oversized memcpy into a stack vpu_jsm_msg buffer, creating kernel memory corruption that can plausibly be leveraged for information disclosure.
- I:HIntegrity impact, high
- The bug is an out-of-bounds stack write from an attacker-influenced firmware IPC buffer, which is defensibly exploitable for kernel control-flow or data integrity compromise.
- A:HAvailability impact, high
- Even without reliable code execution, the oversized kernel memcpy can corrupt the stack or fault while reading/writing far beyond the buffers, causing an oops or panic.