Local memory corruption via partial VCE address patch
Published Jul 19, 2026 · Updated Jul 19, 2026
Memory corruption in the Linux Kernel AMDGPU VCE path allows local users to read or corrupt GPU-accessible memory via crafted commands. amdgpu_vce_cs_reloc patches a 64-bit firmware address without first rejecting either out-of-range low or high relocation index. Access to an AMDGPU render node is required; the malformed address lets VCE firmware DMA outside the validated buffer object, causing disclosure, corruption, GPU hangs or resets, and kernel failure.
Summary
What happened
Memory corruption in the Linux Kernel AMDGPU VCE path allows local users to read or corrupt GPU-accessible memory via crafted commands. amdgpu_vce_cs_reloc patches a 64-bit firmware address without first rejecting either out-of-range low or high relocation index. Access to an AMDGPU render node is required; the malformed address lets VCE firmware DMA outside the validated buffer object, causing disclosure, corruption, GPU hangs or resets, and kernel failure.
The record
- CVE
- CVE-2026-53375
- Published
- Jul 19, 2026
- Updated
- Jul 19, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- T1106
- 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=0 <6.1.175
- Affected versionversion=0 <6.12.90
- Affected versionversion=0 <6.18.32
- Affected versionversion=0 <6.6.140
- Affected versionversion=0 <7.0.9
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <0ee17150763962671f43a62ddf8f6ea1feaff438
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <2d66d1f5d8c0434e9a5ad21cc6eaf3a5e32141d5
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <944db9cfa5373f67eb94621d4c2eee572c05fa3f
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <b3d1a0a45c4aec484fa2a5b060b611e3d3064470
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <de2a02cc28d6d5d37db07d00a9a684c754a5fd74
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <ea2c554e700b86a04534b4c24ece5844e8c5f07e
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