CVE-2026-53374

drm/amdgpu: zero-initialize GART table on allocation

HIGH
8.8
CVSS Score
Published: July 19, 2026 at 10:01 AM UTC
Updated: October 19, 2026 at 08:19 PM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH8.8
Exploit prediction
EPSS 0.1%
SSVC
No known exploit

Description

In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu: zero-initialize GART table on allocation GART TLB is flushed after unmapping but not after mapping. Since amdgpu_bo_create_kernel() does not zero-initialize the buffer, when a single PTE is written the TLB may speculatively load other uninitialized entries from the same cacheline. Those garbage entries can appear valid, and a subsequent write to another PTE in the same cacheline may cause the GPU to use a stale garbage PTE from the TLB. Fix this by calling memset_io() to zero-initialize the GART table with gart_pte_flags immediately after allocation. Using AMDGPU_GEM_CREATE_VRAM_CLEARED, SDMA-based clear will not work since SDMA needs GART to be initialized to work. (cherry picked from commit d9af8263b82b6eaa60c5718e0c6631c5037e4b24)

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

4.2 ≤ v < 6.1.1756.13 ≤ v < 6.18.326.19 ≤ v < 7.0.96.2 ≤ v < 6.6.1406.7 ≤ v < 6.12.907.17.1 rc17.1 rc2d38ceaf99ed015f2a0b9af3499791bd3a3daae21
Vendor states this is fixed in 40df11255d71b02e20e70579f1b12b687e396e26 (fixed)
Vendor states this is fixed in 791941be5da125d9a1b228582bfdc300c05d05b3 (fixed)
Vendor states this is fixed in 8ae8b9e74bab94aab1d79f1688129bcc61c8b29a (fixed)
Vendor states this is fixed in 91fbb5e635c8fb1b49e15c19da06480089ef719f (fixed)
Vendor states this is fixed in b17175d0a375b3ed5e81597dac4983fdb46e478d (fixed)
Vendor states this is fixed in e6c2e6c2e1fa066968a16aca1cb66cd1bdde7741 (fixed)
Vendor states this is fixed in 4.2 (unaffected)
Vendor states this is fixed in 6.1.175 (unaffected)
Vendor states this is fixed in 6.12.90 (unaffected)
Vendor states this is fixed in 6.18.32 (unaffected)
Vendor states this is fixed in 6.6.140 (unaffected)
Vendor states this is fixed in 7.0.9 (unaffected)
Vendor states this is fixed in 7.1 (unaffected)

SSVC — Action Prioritization

SSVCNo known exploitNot automatableTotal impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

8.8HIGHLinux
Vector?

Quick Info

StatusMODIFIED
CWE
NVD-CWE-noinfoCWE-457

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card