Local DMA isolation bypass via signed error mishandling
Published Jul 19, 2026 · Updated Jul 19, 2026
Improper error handling in Linux Kernel msm DRM IOMMU mapping allows local users to read or corrupt physical memory through GPU or display DMA. msm_iommu_map() stores a signed-negative iommu_map_sgtable() result in size_t, treating the failure as a successful mapping length instead of returning it. Exploitation requires access to a Qualcomm DRM device node and attacker-induced IOMMU exhaustion; consequences include physical-memory disclosure or corruption, GPU hangs, display stalls, and kernel oopses.
Summary
What happened
Improper error handling in Linux Kernel msm DRM IOMMU mapping allows local users to read or corrupt physical memory through GPU or display DMA. msm_iommu_map() stores a signed-negative iommu_map_sgtable() result in size_t, treating the failure as a successful mapping length instead of returning it. Exploitation requires access to a Qualcomm DRM device node and attacker-induced IOMMU exhaustion; consequences include physical-memory disclosure or corruption, GPU hangs, display stalls, and kernel oopses.
The record
- CVE
- CVE-2026-64153
- Published
- Jul 19, 2026
- Updated
- Jul 19, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- T1068
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jul 19, 2026CVE publishedPublication date reported by the CVE source.
- Jul 19, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=5.15
- Affected versionversion=ad8f36e4b6b1c826a0daa5fda2c5839205b5aa8b <3457807aeb88077712f0a7cb65c3ca5120773d75
- Affected versionversion=ad8f36e4b6b1c826a0daa5fda2c5839205b5aa8b <3a45af37733446e114bf19b0209fe7d8089bdb8b
- Affected versionversion=ad8f36e4b6b1c826a0daa5fda2c5839205b5aa8b <3c2cdb7c07f664b77e2a75b50793b845d5742efa
- Affected versionversion=ad8f36e4b6b1c826a0daa5fda2c5839205b5aa8b <3e3c3c95ef4fe17231a9149e27bcfc9dae2dd89f
- Affected versionversion=ad8f36e4b6b1c826a0daa5fda2c5839205b5aa8b <55e0f0d1c1a4ee1e46da7da4d443eb3044fb3851
- Affected versionversion=ad8f36e4b6b1c826a0daa5fda2c5839205b5aa8b <7256e54583aee21e23929e7554278c2f5c1a08b1
- Affected versionversion=ad8f36e4b6b1c826a0daa5fda2c5839205b5aa8b <f4e37f3df436c2bdd2621c21f9c72c8f149a221d
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo