Look up another CVE · open CVE-2026-64039 in the interactive tracker
CVE-2026-64039
drm/msm/snapshot: fix dumping of the unaligned regions
Published 2026-07-19 (3 months ago) by the Linux kernel CNA. Subsystem drivers/gpu. Debian urgency: not yet assigned.
What to do, per Debian release
Debian's own status for CVE-2026-64039 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 | fixed | 6.1.176-1 | Update the kernel and reboot. Fixed 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.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
The snapshotting code internally aligns data segment to 16 bytes. This works fine for DPU code (where most of the regions are aligned), but fails for snapshotting of the DSI data (because DSI data region is shifted by 4 bytes). Fix the code by removing length alignment and by accurately printing last registers in the region. While reworking the code also fix the 16x memory overallocation in msm_disp_state_dump_regs(). Patchwork: https://patchwork.freedesktop.org/patch/725449/
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/msm_disp_snapshot_util.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.7 high
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:Hsource recompute it - Attack vector
- local (AV:L)source
- EPSS
- 0.18%, higher than 7.6% 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.14 | 5.15.209 | 8fb070cf9584 |
| 5.14 | 6.1.175 | cecd34e04612 |
| 5.14 | 6.6.142 | 070e40acc59e |
| 5.14 | 6.12.92 | 1ef79be77470 |
| 5.14 | 6.18.34 | cdd1aaf0ee96 |
| 5.14 | 7.0.11 | 0c90ececfad3 |
| 5.14 | 7.1 | 76824d2467fe |
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 only from kernel-local display debug/snapshot paths (error handlers, debugfs, devcoredump) in the MSM DRM/KMS driver, not from any network protocol.
- AC:LAttack complexity, low
- On affected Qualcomm DSI 6G hardware the 4-byte register offset makes region sizes non-16-byte-aligned predictably, so once a display snapshot is triggered the out-of-bounds MMIO read and 16× over-allocation occur reliably without attacker-dependent race or layout conditions.
- PR:NPrivileges required, none
- Snapshot capture is invoked automatically on display error IRQ/workqueue paths that can be induced by an unprivileged local app stressing the GPU/display pipeline on Android/embedded MSM devices, without root, capabilities, or debugfs access.
- UI:NUser interaction, none
- Exploitation requires no victim interaction beyond normal device use; display-error snapshots fire from kernel error handlers without the user opening files or mounting filesystems.
- S:UScope, unchanged
- Impact is confined to kernel/driver state on the local host (crash, MMIO OOB read, memory pressure); it does not cross a VM, container, or IOMMU security boundary.
- C:HConfidentiality impact, high
- The bug performs out-of-bounds MMIO reads past the mapped DSI register window (up to the alignment padding per block), storing returned hardware register values into the kernel snapshot buffer that is later exposed via devcoredump.
- I:NIntegrity impact, none
- The flaw is an out-of-bounds read and erroneous allocation sizing only; it does not corrupt kernel memory or provide a write primitive.
- A:HAvailability impact, high
- Out-of-bounds MMIO accesses can provoke synchronous external aborts/kernel oops on ARM platforms, and the 16× per-block over-allocation during error snapshots can exhaust kernel memory and crash or hang the system.