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.
Affected products
Version statuses are supplied by the assigning organization. Consult the original record for detailed ranges and platform conditions.
Linux Linux
Default version status: unaffected
6856e4b65f64eeb3f17148f79b36c1d60c627529 to < 1db431380879fd9d28b763a88a0c0431be5be8dfaffected6856e4b65f64eeb3f17148f79b36c1d60c627529 to < 32b153658f017ad2f5bf8aab479e8d16ac95bc3aaffected6856e4b65f64eeb3f17148f79b36c1d60c627529 to < 77d0b5d11387071770246fd0185a69fa28e8e109affected6856e4b65f64eeb3f17148f79b36c1d60c627529 to < 047d44d8d29a6a1a5757256837aa9dd78e3cd0b5affected6856e4b65f64eeb3f17148f79b36c1d60c627529 to < ad52d61d82181dbdb7f05826de38352d5e550cc2affected
Linux Linux
Default version status: affected
5.4affected0 to < 5.4unaffected6.6.140 to ≤ 6.6.*unaffected6.12.90 to ≤ 6.12.*unaffected6.18.32 to ≤ 6.18.*unaffected7.0.9 to ≤ 7.0.*unaffected7.1 to ≤ *unaffected
References
- https://git.kernel.org/stable/c/1db431380879fd9d28b763a88a0c0431be5be8df ↗
- https://git.kernel.org/stable/c/32b153658f017ad2f5bf8aab479e8d16ac95bc3a ↗
- https://git.kernel.org/stable/c/77d0b5d11387071770246fd0185a69fa28e8e109 ↗
- https://git.kernel.org/stable/c/047d44d8d29a6a1a5757256837aa9dd78e3cd0b5 ↗
- https://git.kernel.org/stable/c/ad52d61d82181dbdb7f05826de38352d5e550cc2 ↗