CVE-2026-46229: Linux kernel · drm/amdkfd: Clear VRAM on allocation to prevent stale data exposure
Affects Linux kernelSource CVE Database V5
Not known to be exploited · fixed in ad52d61d82181dbdb7f05826de38352d5e550cc2 : update Linux kernel when convenient.
Data as of 30 Oct 2026, 12:36 UTC
Rated Medium by Threat Radar's AI analysis · No CVSS score from NVD or the CNA
Thin evidence
One scorer or none- Patch
- Available – fixed in ad52d61d82181dbdb7f05826de38352d5e550cc2, 77d0b5d11387071770246fd0185a69fa28e8e109, 047d44d8d29a6a1a5757256837aa9dd78e3cd0b5 +3
Exploitation evidence
Disclosed: evidence found.
CVE published 28 May 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
AI-suggested
A fix is available and has been applied in the Linux kernel source as indicated by the fixed commit versions. Users should update to a Linux kernel version that includes these fixes to prevent stale VRAM data exposure and related crashes.
Description
A vulnerability in the Linux kernel's AMD KFD VRAM allocation was fixed to prevent exposure of stale data. Previously, VRAM allocated via the KFD path did not clear old data, allowing residual information from prior use to be visible to compute kernels. This could cause crashes in RCCL P2P transport due to corrupted protocol handshake fields.
References
- git.kernel.org/stable/c/6bcf59545c84a5105d14d59f40069ef4c033584e (opens in a new tab)
- git.kernel.org/stable/c/1db431380879fd9d28b763a88a0c0431be5be8df (opens in a new tab)
- git.kernel.org/stable/c/32b153658f017ad2f5bf8aab479e8d16ac95bc3a (opens in a new tab)
- git.kernel.org/stable/c/77d0b5d11387071770246fd0185a69fa28e8e109 (opens in a new tab)
- git.kernel.org/stable/c/047d44d8d29a6a1a5757256837aa9dd78e3cd0b5 (opens in a new tab)
- git.kernel.org/stable/c/ad52d61d82181dbdb7f05826de38352d5e550cc2 (opens in a new tab)