---
id: CVE-2026-46229
title: 'drm/amdkfd: Clear VRAM on allocation to prevent stale data exposure'
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_CLEA…
severity: none
vendor: Linux
product: Linux
affected:
  - >-
    Linux >= 6856e4b65f64eeb3f17148f79b36c1d60c627529 <
    6bcf59545c84a5105d14d59f40069ef4c033584e
  - >-
    Linux >= 6856e4b65f64eeb3f17148f79b36c1d60c627529 <
    1db431380879fd9d28b763a88a0c0431be5be8df
  - >-
    Linux >= 6856e4b65f64eeb3f17148f79b36c1d60c627529 <
    32b153658f017ad2f5bf8aab479e8d16ac95bc3a
  - >-
    Linux >= 6856e4b65f64eeb3f17148f79b36c1d60c627529 <
    77d0b5d11387071770246fd0185a69fa28e8e109
  - >-
    Linux >= 6856e4b65f64eeb3f17148f79b36c1d60c627529 <
    047d44d8d29a6a1a5757256837aa9dd78e3cd0b5
  - >-
    Linux >= 6856e4b65f64eeb3f17148f79b36c1d60c627529 <
    ad52d61d82181dbdb7f05826de38352d5e550cc2
  - Linux 5.4
ssvc:
  exploitation: none
  automatable: 'no'
  technicalImpact: partial
  timestamp: '2026-11-06T16:12:32.118593Z'
published: '2026-05-28'
updated: '2026-11-06'
sourceUpdated: '2026-11-06T16:13:45.647Z'
source: CVEORG
sourceUrl: 'https://www.cve.org/CVERecord?id=CVE-2026-46229'
references:
  - url: 'https://git.kernel.org/stable/c/6bcf59545c84a5105d14d59f40069ef4c033584e'
  - url: 'https://git.kernel.org/stable/c/1db431380879fd9d28b763a88a0c0431be5be8df'
  - url: 'https://git.kernel.org/stable/c/32b153658f017ad2f5bf8aab479e8d16ac95bc3a'
  - url: 'https://git.kernel.org/stable/c/77d0b5d11387071770246fd0185a69fa28e8e109'
  - url: 'https://git.kernel.org/stable/c/047d44d8d29a6a1a5757256837aa9dd78e3cd0b5'
  - url: 'https://git.kernel.org/stable/c/ad52d61d82181dbdb7f05826de38352d5e550cc2'
tags:
  - cve.org
epss: 0.00119
epssPercentile: 0.01779
ingestedAt: '2026-11-05T15:02:32.325Z'
---

## Overview

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

- `Linux >= 6856e4b65f64eeb3f17148f79b36c1d60c627529 < 6bcf59545c84a5105d14d59f40069ef4c033584e`
- `Linux >= 6856e4b65f64eeb3f17148f79b36c1d60c627529 < 1db431380879fd9d28b763a88a0c0431be5be8df`
- `Linux >= 6856e4b65f64eeb3f17148f79b36c1d60c627529 < 32b153658f017ad2f5bf8aab479e8d16ac95bc3a`
- `Linux >= 6856e4b65f64eeb3f17148f79b36c1d60c627529 < 77d0b5d11387071770246fd0185a69fa28e8e109`
- `Linux >= 6856e4b65f64eeb3f17148f79b36c1d60c627529 < 047d44d8d29a6a1a5757256837aa9dd78e3cd0b5`
- `Linux >= 6856e4b65f64eeb3f17148f79b36c1d60c627529 < ad52d61d82181dbdb7f05826de38352d5e550cc2`
- `Linux 5.4`

## Remediation

Refer to the linked advisories for vendor-supplied fixes and affected version ranges.