Look up another CVE · open CVE-2026-64050 in the interactive tracker
CVE-2026-64050
drm/msm/dpu: don't mix devm and drmm functions
Published 2026-07-19 (3 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-64050 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.12-1 | Update the kernel and reboot. Fixed in 7.0.12-1. A running kernel keeps the old code until the machine restarts. |
| Debian unstablesid | fixed | 7.0.12-1 | Update the kernel and reboot. Fixed in 7.0.12-1. A running kernel keeps the old code until the machine restarts. |
The vulnerability
What the bug is
Mixing devm and drmm functions will result in a use-after-free on msm driver teardown if userspace keeps a reference on the drm device: The WB connector data will be destroyed because of the use of devm_kzalloc()), while the usersoace still can try interacting with the WB connector (which uses drmm_ functions). Change dpu_writeback_init() to use drmm_. Patchwork: https://patchwork.freedesktop.org/patch/722656/
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/disp/dpu1/dpu_writeback.c
- What this is
- DRM DRIVER for Qualcomm display hardwareMAINTAINERS section matched on drivers/gpu/drm/msm/ · linux-arm-msm@vger.kernel.org · Maintained
Show whether Debian builds this, per release
Not established. This site could not find the build rule for the affected file in the kernel trees Debian ships, so it has no answer about whether Debian compiles this code. Read that as unknown, never as absent.
- bookworm, trixie, forky, sid?
- ?
- not established - no Makefile entry for the affected file
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.
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
Signals
- Published
- 2026-07-19 (3 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.17%, higher than 5.8% 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.18 | 6.18.34 | ff58e5ef1b46 |
| 6.18 | 7.0.11 | 95048a12f48c |
| 6.18 | 7.1 | c0c70a11365c |
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 reachable only through local DRM character device ioctls on /dev/dri/card0 during driver teardown, not via any network protocol or physical bus.
- AC:LAttack complexity, low
- An attacker who keeps a DRM file descriptor open controls the userspace side of the race and can repeatedly issue ioctls during the teardown window; UAF exploitation does not depend on winning a race the attacker cannot influence.
- PR:LPrivileges required, low
- Exploitation requires only local access to the primary DRM device node (typically membership in the video/render group on Linux); no real root or init-namespace capabilities are needed to hold the fd and trigger UAF via connector query ioctls.
- UI:NUser interaction, none
- No victim interaction is required beyond the attacker maintaining their own open DRM file descriptor during driver unload or unbind.
- S:UScope, unchanged
- The vulnerability causes kernel memory corruption and potential local privilege escalation within the same kernel security boundary, not a cross-boundary escape such as VM or IOMMU bypass.
- C:HConfidentiality impact, high
- Use-after-free of the dpu_wb_connector structure allows reading freed slab memory and can be leveraged for arbitrary kernel memory disclosure through heap grooming.
- I:HIntegrity impact, high
- UAF corruption of connector private data and the wb_enc pointer can be turned into arbitrary kernel writes or code execution, and the writeback path can program display hardware DMA to attacker-influenced addresses.
- A:HAvailability impact, high
- Dereferencing the freed dpu_wb_connector during ioctl handling can cause kernel oops or panic, and UAF exploitation attempts reliably threaten system availability.