Look up another CVE · open CVE-2026-53203 in the interactive tracker
CVE-2026-53203
accel/ivpu: Add buffer overflow check in MS get_info_ioctl
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-53203 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 the info size returned from the metric stream info query is not exceeded when checked against the allocated buffer size. If the firmware returns a size larger than the buffer, reject the operation with -EOVERFLOW instead of proceeding with an incorrect buffer copy.
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_ms.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.14%, higher than 3.2% 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.11 | 6.12.94 | d3c12ed33e89 |
| 6.11 | 6.18.36 | fa598556ecef |
| 6.11 | 7.0.13 | 4e5047cc94be |
| 6.11 | 7.1 | fb1764258376 |
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 path is a DRM accel ioctl on the local `/dev/accel/accel*` device, reached through `DRM_IOCTL_IVPU_METRIC_STREAMER_GET_INFO`. It is not reachable over the network or by adjacent/physical input.
- AC:LAttack complexity, low
- The attacker controls the ioctl arguments, including the metric group mask and user buffer size, and there is no race or hard-to-win timing condition. Triggering the overlong copy depends on normal firmware response data for selected metrics, not on conditions outside the attacker’s control in the vulnerable path.
- PR:LPrivileges required, low
- A local user with access to the accelerator device node can open the device and issue the ioctl; the driver ioctl has no capability, master, or root-only check. This does not require real root/admin privileges.
- UI:NUser interaction, none
- After the attacker has local access to the device node, exploitation is performed directly by issuing ioctls. No victim action such as opening a file or mounting a filesystem is required.
- S:UScope, unchanged
- The issue is within the kernel driver and impacts kernel-managed resources on the same system. It is not a VM escape, IOMMU boundary bypass, or cross-authority scope change.
- C:HConfidentiality impact, high
- The firmware-reported `info_size` was used as the `copy_to_user()` length without verifying it fits in the fixed 64 KiB kernel buffer, enabling an out-of-bounds kernel read into userspace. Under the higher-severity rule, this is treated as high confidentiality impact because adjacent kernel memory may be disclosed.
- I:NIntegrity impact, none
- The vulnerable host-side operation is an overlong copy from kernel memory to userspace, and the fix prevents that incorrect buffer copy. No kernel write primitive or data modification path is evident from this bug.
- A:HAvailability impact, high
- An overlong kernel-source copy can run past the mapped buffer into invalid or sensitive kernel virtual memory and may fault or destabilize the kernel. Under the required higher-severity rule, the plausible local DoS impact is scored high.