Kernel memory corruption via uninitialized VCE size
Published Jul 30, 2024 · Updated May 11, 2026
Use of an uninitialized value in Linux 4.2 and later allows local users to corrupt kernel memory through crafted AMDGPU VCE commands. The AMDGPU VCE command parser can pass an uninitialized frame size to amdgpu_vce_cs_reloc, weakening its buffer-size validation. The path requires low-privileged local access and VCE-capable AMD hardware; the resulting out-of-bounds GPU write can crash the kernel or corrupt privileged memory.
Summary
What happened
Use of an uninitialized value in Linux 4.2 and later allows local users to corrupt kernel memory through crafted AMDGPU VCE commands. The AMDGPU VCE command parser can pass an uninitialized frame size to amdgpu_vce_cs_reloc, weakening its buffer-size validation. The path requires low-privileged local access and VCE-capable AMD hardware; the resulting out-of-bounds GPU write can crash the kernel or corrupt privileged memory.
The record
- CVE
- CVE-2024-42228
- Published
- Jul 30, 2024
- Updated
- May 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-908, T1068
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jul 30, 2024CVE publishedPublication date reported by the CVE source.
- May 11, 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=4.2
- Affected versionversion=d38ceaf99ed015f2a0b9af3499791bd3a3daae21 <3b505759447637dcccb50cbd98ec6f8d2a04fc46
- Affected versionversion=d38ceaf99ed015f2a0b9af3499791bd3a3daae21 <855ae72c20310e5402b2317fc537d911e87537ef
- Affected versionversion=d38ceaf99ed015f2a0b9af3499791bd3a3daae21 <88a9a467c548d0b3c7761b4fd54a68e70f9c0944
- Affected versionversion=d38ceaf99ed015f2a0b9af3499791bd3a3daae21 <9ee1534ecdd5b4c013064663502d7fde824d2144
- Affected versionversion=d38ceaf99ed015f2a0b9af3499791bd3a3daae21 <d35cf41c8eb5d9fe95b21ae6ee2910f9ba4878e8
- Affected versionversion=d38ceaf99ed015f2a0b9af3499791bd3a3daae21 <da6a85d197888067e8d38b5d22c986b5b5cab712
- Affected versionversion=d38ceaf99ed015f2a0b9af3499791bd3a3daae21 <df02642c21c984303fe34c3f7d72965792fb1a15
- Affected versionversion=d38ceaf99ed015f2a0b9af3499791bd3a3daae21 <f8f120b3de48b8b6bdf8988a9b334c2d61c17440
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