Skip to main content
VulnerabilityPublished Updated

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

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-46229· Medium

Not known to be exploited · CVSS 5.5 Medium · fixed in ad52d61d82181dbdb7f05826de38352d5e550cc2 : update Linux kernel when convenient.

Data as of 30 Oct 2026, 16:33 UTC

CVSS 3.1 base score
5.5Medium
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
Patch
Available – fixed in ad52d61d82181dbdb7f05826de38352d5e550cc2, 77d0b5d11387071770246fd0185a69fa28e8e109, 047d44d8d29a6a1a5757256837aa9dd78e3cd0b5 +3
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 28 May 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ 6856e4b65f64eeb3f17148f79b36c1d60c627529, < ad52d61d82181dbdb7f05826de38352d5e550cc2
Fixed in
  • ad52d61d82181dbdb7f05826de38352d5e550cc2
LinuxLinuxAffected
  • ≥ 6856e4b65f64eeb3f17148f79b36c1d60c627529, < 77d0b5d11387071770246fd0185a69fa28e8e109
Fixed in
  • 77d0b5d11387071770246fd0185a69fa28e8e109
LinuxLinuxAffected
  • ≥ 6856e4b65f64eeb3f17148f79b36c1d60c627529, < 047d44d8d29a6a1a5757256837aa9dd78e3cd0b5
Fixed in
  • 047d44d8d29a6a1a5757256837aa9dd78e3cd0b5
LinuxLinuxAffected
  • ≥ 6856e4b65f64eeb3f17148f79b36c1d60c627529, < 32b153658f017ad2f5bf8aab479e8d16ac95bc3a
Fixed in
  • 32b153658f017ad2f5bf8aab479e8d16ac95bc3a
LinuxLinuxAffected
  • ≥ 6856e4b65f64eeb3f17148f79b36c1d60c627529, < 6bcf59545c84a5105d14d59f40069ef4c033584e
Fixed in
  • 6bcf59545c84a5105d14d59f40069ef4c033584e
LinuxLinuxAffected
  • ≥ 6856e4b65f64eeb3f17148f79b36c1d60c627529, < 1db431380879fd9d28b763a88a0c0431be5be8df
Fixed in
  • 1db431380879fd9d28b763a88a0c0431be5be8df

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

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.

References

Community reviews

Loading reviews…