Local data exposure via uncleared KFD VRAM
Published May 28, 2026 · Updated May 28, 2026
Improper VRAM initialization in affected Linux Kernel releases allows local users to read stale GPU memory through KFD allocations. The KFD allocation path sets AMDGPU_GEM_CREATE_VRAM_WIPE_ON_RELEASE but omits AMDGPU_GEM_CREATE_VRAM_CLEARED, leaving prior VRAM and page-table contents in new user buffers. Reachability requires local compute access through AMD KFD; exposed stale data can corrupt RCCL P2P ptrExchange, head, or tail fields and crash the transport handshake.
Summary
What happened
Improper VRAM initialization in affected Linux Kernel releases allows local users to read stale GPU memory through KFD allocations. The KFD allocation path sets AMDGPU_GEM_CREATE_VRAM_WIPE_ON_RELEASE but omits AMDGPU_GEM_CREATE_VRAM_CLEARED, leaving prior VRAM and page-table contents in new user buffers. Reachability requires local compute access through AMD KFD; exposed stale data can corrupt RCCL P2P ptrExchange, head, or tail fields and crash the transport handshake.
The record
- CVE
- CVE-2026-46229
- Published
- May 28, 2026
- Updated
- May 28, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- T1005
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- May 28, 2026CVE publishedPublication date reported by the CVE source.
- May 28, 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.12.90
- Affected versionversion=0 <6.18.32
- Affected versionversion=0 <6.6.140
- Affected versionversion=0 <7.0.9
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <047d44d8d29a6a1a5757256837aa9dd78e3cd0b5
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <1db431380879fd9d28b763a88a0c0431be5be8df
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <32b153658f017ad2f5bf8aab479e8d16ac95bc3a
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <77d0b5d11387071770246fd0185a69fa28e8e109
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <ad52d61d82181dbdb7f05826de38352d5e550cc2
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