Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

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

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.

Timeline

  1. ID reserved

    By Linux

  2. · 15 days later

    Published

  3. · 5 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2026-46229, by who scored it
Scored byCVSSScoreVector
NVDNVD · Modified3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.12% · top 98% of all CVEs (15 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.

Affected products

  • Linux · Linux

    • affected 6856e4b65f64eeb3f17148f79b36c1d60c627529 – < 6bcf59545c84a5105d14d59f40069ef4c033584e
    • affected 6856e4b65f64eeb3f17148f79b36c1d60c627529 – < 1db431380879fd9d28b763a88a0c0431be5be8df
    • affected 6856e4b65f64eeb3f17148f79b36c1d60c627529 – < 32b153658f017ad2f5bf8aab479e8d16ac95bc3a
    • affected 6856e4b65f64eeb3f17148f79b36c1d60c627529 – < 77d0b5d11387071770246fd0185a69fa28e8e109
    • affected 6856e4b65f64eeb3f17148f79b36c1d60c627529 – < 047d44d8d29a6a1a5757256837aa9dd78e3cd0b5
    • affected 6856e4b65f64eeb3f17148f79b36c1d60c627529 – < ad52d61d82181dbdb7f05826de38352d5e550cc2
  • Linux · Linux

    • affected 5.4
    • unaffected < 5.4
    • unaffected 6.1.191 – ≤ 6.1.*
    • unaffected 6.6.140 – ≤ 6.6.*
    • unaffected 6.12.90 – ≤ 6.12.*
    • unaffected 6.18.32 – ≤ 6.18.*
    • unaffected 7.0.9 – ≤ 7.0.*
    • unaffected 7.1 – ≤ *

References

References6

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-46229 badge
[![CVE-2026-46229](https://cveledger.app/badge/CVE-2026-46229.svg)](https://cveledger.app/cve/CVE-2026-46229)

Record last updated .