drm/amdkfd: Clear VRAM on allocation to prevent stale data exposure
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 6856e4b65f64eeb3f17148f79b36c1d60c627529 · < ad52d61d82181dbdb7f05826de38352d5e550cc2| No fix yet |
| Linux Linux |
|
|
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.
From the CVE record · Linux
Linux kernel KFD VRAM allocations do not clear newly allocated VRAM, allowing compute kernels to observe stale data from prior use. This affects local users making KFD VRAM allocations and can also cause RCCL P2P transport crashes.
Operators running Linux kernels with the affected amdkfd KFD VRAM allocation path should check their versions against the vendor advisory.