VulnerabilityPublished 24 Jul 2026

CVE-2026-64231: Linux kernel · drm/msm/dsi: don't dump registers past the mapped region

Affects Linux kernelSource GCVE Database

Compare

Not known to be exploited.

Data as of 8 Nov 2026, 20:49 UTC

Severity

Medium

Rated Medium by Threat Radar's AI analysis · No CVSS score from NVD or the CNA

Thin evidence

One scorer or none

Exploitation evidence

Disclosed: evidence found.
CVE published 24 Jul 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 8 Nov 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

AI-suggested

A fix has been implemented in the Linux kernel to address this issue by adjusting the memory dump size to prevent access beyond the mapped IO region. Users should apply the official kernel patch referenced in the Patchwork link to remediate this vulnerability.

Description

A vulnerability in the Linux kernel's drm/msm/dsi component could cause memory dumping operations to access unmapped IO address regions due to improper size adjustment when an internal io_offset is applied. This issue has been fixed by lowering the control size by the io_offset value to prevent out-of-bounds access.

Impact

This vulnerability could cause the kernel to access unmapped memory regions during diagnostic register dumps, potentially leading to kernel crashes or undefined behavior. There is no indication of privilege escalation or arbitrary code execution from the provided data. No known exploits in the wild have been reported.

Summary

The Linux kernel's drm/msm/dsi driver on DSI 6G platforms internally adjusts the IO address space by an io_offset. However, the size used for memory dumping was not adjusted accordingly, potentially allowing access beyond the mapped region. This could lead to attempts to read unmapped memory areas during register dumps. The fix involves reducing the ctrl_size by the io_offset to ensure memory dumps do not exceed the mapped IO region boundaries. The patch modifies functions related to msm_disp_snapshot and msm_dsi_snapshot to enforce this boundary check.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Description

AI analysisMachine-generated, updated 8 Nov 2026, 20:49 UTC

Technical details

References

Community reviews

Related threats