drm/amdkfd: Clear VRAM on allocation to prevent stale data exposure
Summary
| CVE | CVE-2026-46229 |
|---|---|
| State | PUBLISHED |
| Assigner | Linux |
| Source Priority | CVE Program / NVD first with legacy fallback |
| Published | 2026-05-28 10:16:38 UTC |
| Updated | 2026-06-10 21:12:21 UTC |
| Description | In the Linux kernel, the following vulnerability has been resolved: drm/amdkfd: Clear VRAM on allocation to prevent stale data exposure KFD VRAM allocations set AMDGPU_GEM_CREATE_VRAM_WIPE_ON_RELEASE but not AMDGPU_GEM_CREATE_VRAM_CLEARED, leaving freshly allocated VRAM with stale data from prior use observable by compute kernels. The GEM ioctl path already sets VRAM_CLEARED for all userspace allocations via amdgpu_gem_create_ioctl() and amdgpu_mode_dumb_create(). The KFD path was missing this flag, allowing stale page table remnants to leak into user buffers. This causes crashes in RCCL P2P transport where non-zero data in ptrExchange/head/tail fields corrupts the protocol handshake. |
Risk And Classification
Primary CVSS: v3.1 5.5 MEDIUM from [email protected]
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS: 0.000180000 probability, percentile 0.050080000 (date 2026-06-02)
Problem Types: NVD-CWE-noinfo
CVSS v3.1 Breakdown
Attack Vector
LocalAttack Complexity
LowPrivileges Required
LowUser Interaction
NoneScope
UnchangedConfidentiality
NoneIntegrity
NoneAvailability
HighCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
NVD Known Affected Configurations (CPE 2.3)
| Type | Vendor | Product | Version | Update | Edition | Language |
|---|---|---|---|---|---|---|
| Operating System | Linux | Linux Kernel | All | All | All | All |
Vendor Declared Affected Products
| Source | Vendor | Product | Version | Platforms |
|---|---|---|---|---|
| CNA | Linux | Linux | affected 6856e4b65f64eeb3f17148f79b36c1d60c627529 1db431380879fd9d28b763a88a0c0431be5be8df git | Not specified |
| CNA | Linux | Linux | affected 6856e4b65f64eeb3f17148f79b36c1d60c627529 32b153658f017ad2f5bf8aab479e8d16ac95bc3a git | Not specified |
| CNA | Linux | Linux | affected 6856e4b65f64eeb3f17148f79b36c1d60c627529 77d0b5d11387071770246fd0185a69fa28e8e109 git | Not specified |
| CNA | Linux | Linux | affected 6856e4b65f64eeb3f17148f79b36c1d60c627529 047d44d8d29a6a1a5757256837aa9dd78e3cd0b5 git | Not specified |
| CNA | Linux | Linux | affected 6856e4b65f64eeb3f17148f79b36c1d60c627529 ad52d61d82181dbdb7f05826de38352d5e550cc2 git | Not specified |
| CNA | Linux | Linux | affected 5.4 | Not specified |
| CNA | Linux | Linux | unaffected 5.4 semver | Not specified |
| CNA | Linux | Linux | unaffected 6.6.140 6.6.* semver | Not specified |
| CNA | Linux | Linux | unaffected 6.12.90 6.12.* semver | Not specified |
| CNA | Linux | Linux | unaffected 6.18.32 6.18.* semver | Not specified |
| CNA | Linux | Linux | unaffected 7.0.9 7.0.* semver | Not specified |
| CNA | Linux | Linux | unaffected 7.1-rc1 * original_commit_for_fix | Not specified |
References
| Reference | Source | Link | Tags |
|---|---|---|---|
| git.kernel.org/stable/c/32b153658f017ad2f5bf8aab479e8d16ac95bc3a | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | Patch |
| git.kernel.org/stable/c/77d0b5d11387071770246fd0185a69fa28e8e109 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | Patch |
| git.kernel.org/stable/c/1db431380879fd9d28b763a88a0c0431be5be8df | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | Patch |
| git.kernel.org/stable/c/047d44d8d29a6a1a5757256837aa9dd78e3cd0b5 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | Patch |
| git.kernel.org/stable/c/ad52d61d82181dbdb7f05826de38352d5e550cc2 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | Patch |
| CVE Program record | CVE.ORG | www.cve.org | canonical |
| NVD vulnerability detail | NVD | nvd.nist.gov | canonical, analysis |
No vendor comments have been submitted for this CVE.
There are currently no legacy QID mappings associated with this CVE.