CVE-2026-46229

Summary

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.

Impact & exploitability

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Affected products we track (1)

Recommendation

Apply the vendor fix in your normal patch cycle. Open any affected product above for its exact safe version.

Official patch: https://git.kernel.org/stable/c/047d44d8d29a6a1a5757256837aa9dd78e3cd0b5 ↗

Additional information

• NVD record
• https://git.kernel.org/stable/c/047d44d8d29a6a1a5757256837aa9dd78e3cd0b5Patch
• https://git.kernel.org/stable/c/1db431380879fd9d28b763a88a0c0431be5be8dfPatch
• https://git.kernel.org/stable/c/32b153658f017ad2f5bf8aab479e8d16ac95bc3aPatch
• https://git.kernel.org/stable/c/77d0b5d11387071770246fd0185a69fa28e8e109Patch
• https://git.kernel.org/stable/c/ad52d61d82181dbdb7f05826de38352d5e550cc2Patch
• https://git.kernel.org/stable/c/6bcf59545c84a5105d14d59f40069ef4c033584e