Look up another CVE · open CVE-2026-53068 in the interactive tracker
CVE-2026-53068
drm/komeda: fix integer overflow in AFBC framebuffer size check
Published 2026-06-24 (4 months ago) by the Linux kernel CNA. Subsystem drivers/gpu. Debian urgency: not yet assigned.
Debian does not build this code. The per-release build detail is under "Where it lives" below.
What to do, per Debian release
Debian's own status for CVE-2026-53068 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 | fixedDLA-4665-1 · 2026-07-03 · text | 6.1.176-1 | Update the kernel and reboot. DLA-4665-1 shipped the fix on 2026-07-03, 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.10-1 | Update the kernel and reboot. Fixed in 7.0.10-1. A running kernel keeps the old code until the machine restarts. |
| Debian unstablesid | fixed | 7.0.10-1 | Update the kernel and reboot. Fixed in 7.0.10-1. A running kernel keeps the old code until the machine restarts. |
The vulnerability
What the bug is
The AFBC framebuffer size validation calculates the minimum required buffer size by adding the AFBC payload size to the framebuffer offset. This addition is performed without checking for integer overflow. If the addition oveflows, the size check may incorrectly succed and allow userspace to provide an undersized drm_gem_object, potentially leading to out-of-bounds memory access. Add usage of check_add_overflow() to safely compute the minimum required size and reject the framebuffer if an overflow is detected. This makes the AFBC size validation more robust against malformed. Found by Linux Verification Center (linuxtesting.org) with SVACE.
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/gpu/drm/arm/display/komeda/komeda_framebuffer.c
- What this is
- ARM KOMEDA DRM-KMS DRIVERMAINTAINERS section matched on drivers/gpu/drm/arm/display/komeda/ · Supported
- Kernel module
- none to look for. The file would have gone into komeda, and Debian does not compile it into that module, so finding komeda in lsmod would say nothing about this CVE.
Check it on the machine
grep -w CONFIG_DRM_KOMEDA /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.
Show whether Debian builds this, per release
Debian does not build this code. In 4 releases below, every kernel flavour Debian publishes has the switch off, so the vulnerable file is compiled into no kernel binary Debian ships.
- bookworm, trixie, forky, sidn
- n
- not enabled on any flavour - this release does not build the code
- Build switch
- CONFIG_DRM_KOMEDA
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-24 (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.17%, higher than 5.5% of all CVEssource
- CISA KEV
- not listedthe KEV catalogue
- Debian urgency
- not yet assignedsource
- Subsystem
- drivers/gpu
Upstream fixes
The versions the CNA records as introducing and fixing this, and the commit for each. source
| Introduced | Fixed in | Commit |
|---|---|---|
| 5.3 | 5.10.258 | a3a2a9bdc0f9 |
| 5.3 | 5.15.209 | e27b58095d7d |
| 5.3 | 6.1.175 | 02ff8a7d3d0e |
| 5.3 | 6.6.141 | d8a541906860 |
| 5.3 | 6.12.91 | 8165e8b28fdf |
| 5.3 | 6.18.33 | fe1f80f8f6e8 |
| 5.3 | 7.0.10 | 872d923b8527 |
| 5.3 | 7.1 | 779ec12c85c9 |
Debian advisories
| Advisory | Date | Shipped to | Debian |
|---|---|---|---|
| DLA-4671-1 | 2026-07-05 | bullseye 6.1.176-1~deb11u1 | tracker |
| DLA-4665-1 | 2026-07-03 | bookworm 6.1.176-1 | tracker |
| DLA-4664-1 | 2026-07-03 | bullseye 5.10.259-1 | tracker |
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 from local userspace through DRM ioctls, specifically framebuffer creation with `DRM_IOCTL_MODE_ADDFB2` on a Komeda DRM device. It is not reachable by network or adjacent-only input.
- AC:LAttack complexity, low
- The attacker controls the framebuffer dimensions, modifier, offset, and GEM handle inputs needed to trigger the integer overflow. No race or external timing condition is required.
- PR:LPrivileges required, low
- The vulnerable `ADDFB2` path has no root, auth, or master ioctl flag, but it requires local access to the DRM device node and a valid GEM handle. Triggering hardware consumption of the framebuffer uses normal local DRM modeset privileges rather than init-namespace root.
- UI:NUser interaction, none
- An attacker with local DRM device access can issue the required ioctls directly. No separate victim action is required.
- S:UScope, unchanged
- The impact remains within the local kernel/device security authority. This is not a VM escape, guest-to-host boundary crossing, or demonstrated IOMMU isolation bypass.
- C:HConfidentiality impact, high
- The overflow can allow an undersized GEM object to pass validation and cause the display engine to DMA-read outside the framebuffer allocation. Because this is an out-of-bounds read from system memory and is not tightly bounded, confidentiality is high.
- I:NIntegrity impact, none
- The reachable AFBC framebuffer use is a display source path, so the hardware consumes memory rather than writing to it. The writeback path rejects AFBC framebuffers through layer capability checks, so a direct out-of-bounds write was not established.
- A:HAvailability impact, high
- Out-of-bounds DMA reads can trigger AXI/TBU/IOMMU faults or wedge the display pipeline, and on some deployments may escalate to a kernel-visible hardware fault. The issue can be triggered repeatedly from local userspace once the device is accessible.