CVE-2026-64039: drm/msm/snapshot: fix dumping of the unaligned regions
In the Linux kernel, the following vulnerability has been resolved:
drm/msm/snapshot: fix dumping of the unaligned regions
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/
Security readout for executives and security teams
Plain-English summary
This is a high-severity Linux kernel issue in the msm DRM snapshot code. Unaligned display snapshot regions can be handled incorrectly during register dumping. The published impact is local, with high confidentiality and availability impact. The source bundle does not show active exploitation.
Executive priority
Treat as a high-priority kernel maintenance issue for affected Linux fleets, especially devices using the msm DRM driver. It is not currently evidenced as exploited, but the potential confidentiality and availability impact justifies timely patch validation.
Technical view
The fix removes length alignment in drm/msm snapshot register dumping and prints final registers accurately. The bug affects unaligned DSI data regions shifted by 4 bytes and also involved a 16x memory overallocation in msm_disp_state_dump_regs(). CVSS 3.1 is 7.7 with no integrity impact stated.
Likely exposure
Exposure appears limited to Linux systems running affected kernel versions with the msm DRM display driver path present or reachable. The bundle lists affected Linux versions from 5.14 through 7.1 ranges, with stable kernel commits referenced as fixes.
Exploitation context
The CVSS vector is local access, low complexity, no privileges, and no user interaction. KEV is false, and the supplied sources provide no evidence of active exploitation, public exploit code, or remote attack exposure.
Researcher notes
The available record is kernel-fix focused and does not provide a CWE, proof of concept, or detailed trigger conditions beyond unaligned msm snapshot register regions. Avoid assuming affected devices beyond Linux kernels carrying the vulnerable drm/msm code path.
Mitigation direction
Identify systems running affected Linux kernel versions.
Prioritize kernels using msm DRM display functionality.
Apply vendor or distribution kernel updates containing the referenced stable commits.
If updates are unavailable, check Linux or distribution guidance for supported mitigations.
Validation and detection
Inventory kernel versions across Linux assets.
Confirm whether msm DRM modules or builds are present.
Map installed kernels against vendor advisories and referenced stable commits.
Verify patched systems include the relevant drm/msm snapshot fix.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cve · low confidence lookup
CVE-2026-64039 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
1CVSS vectors
3Timeline events
0ADP providers
8Source links
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.