Look up another CVE · open CVE-2026-53054 in the interactive tracker
CVE-2026-53054
drm/msm: Fix VM_BIND UNMAP locking
Published 2026-06-24 (4 months ago) by the Linux kernel CNA. Subsystem drivers/gpu. Debian urgency: unimportant.
What to do, per Debian release
Debian's own status for CVE-2026-53054 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 | not affected | 6.12.113-1 | Nothing to do. trixie never shipped the vulnerable code. |
| 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
Wrong argument meant that the objs involved in UNMAP ops were not always getting locked. Since _NO_SHARE objs share a common resv with the VM (which is always locked) this would only show up with non-_NO_SHARE BOs. Patchwork: https://patchwork.freedesktop.org/patch/713898/
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/msm/msm_gem_vma.c
- What this is
- DRM DRIVER for Qualcomm display hardwareMAINTAINERS section matched on drivers/gpu/drm/msm/ · linux-arm-msm@vger.kernel.org · Maintained
- Kernel module
- msm
Check it on the machine
grep -w CONFIG_DRM_MSM /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 msmPrints 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.
- bookwormMnot built on amd64/amd64, amd64/cloud-amd64, amd64/rt/amd64, arm64/cloud-arm64, armhf/armmp, armhf/armmp-lpae, armhf/rt/armmp, i386/686, i386/686-pae, i386/rt/686-pae, ppc64el/powerpc64le
- trixieMnot built on amd64/amd64, amd64/cloud-amd64, amd64/rt/amd64, arm64/cloud-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/amd64, amd64/cloud-amd64, amd64/rt-amd64, arm64/cloud-arm64, armhf/armmp, armhf/armmp-lpae, loong64/loong64, ppc64el/powerpc64le, ppc64el/powerpc64le-64k, riscv64/riscv64, s390x/s390x
- M
- a module where it is built at all; some flavours do not build it
- Build switch
- CONFIG_DRM_MSM
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.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.13%, higher than 2.6% of all CVEssource
- CISA KEV
- not listedthe KEV catalogue
- Debian urgency
- unimportantsource
- 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 |
|---|---|---|
| 6.17 | 6.18.33 | 206f812ef140 |
| 6.17 | 7.0.10 | d9ecf7582705 |
| 6.17 | 7.1 | 85042c2cd970 |
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 the DRM MSM VM_BIND ioctl on a local render/device node, not through network or adjacent/physical input.
- AC:LAttack complexity, low
- The attacker controls the ioctl sequence, VM_BIND opt-in, submitqueue creation, mapped BOs, and crafted UNMAP range; the missed locking is directly selected by attacker-controlled fields and any needed concurrency can be created locally.
- PR:LPrivileges required, low
- The ioctl is DRM_RENDER_ALLOW and has no capability check, but the attacker must be a local user/process with access to the MSM DRM render device.
- UI:NUser interaction, none
- No victim action is required once the attacker can issue the local DRM ioctls.
- S:UScope, unchanged
- This is a kernel DRM/GPUVM locking flaw whose likely consequences remain within the same kernel security authority; it is not a guest-to-host escape or direct IOMMU boundary bypass.
- C:HConfidentiality impact, high
- Missing reservation locking around UNMAP/remap can race GPUVA list operations and VMA freeing for shareable BOs, creating use-after-free/list-corruption conditions that can be leveraged for kernel memory disclosure.
- I:HIntegrity impact, high
- The same unsynchronized GPUVM/GEM list manipulation and freed-object reuse can plausibly provide kernel memory corruption suitable for arbitrary write or control-flow compromise.
- A:HAvailability impact, high
- The bug can corrupt kernel GPUVM/GEM metadata or trigger use-after-free/oops conditions from local ioctls, leading to a kernel crash or hang.