CVE-2026-53374drm/amdgpu: zero-initialize GART table on allocation
- 8.8HighCVSS base score
- 0.13%Exploitation in 30 daysEPSS · top 98% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
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)
Timeline
ID reserved
By Linux
- 40 days later
· 40 days later
Published
- 3 months later
· 3 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
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| LinuxCNA (assigner) | 3.1 | High8.8 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H |
| NVDNVD · Modified | 3.1 | High8.8 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H |
- EPSS (exploitation in 30 days)
- 0.13% · top 98% of all CVEs (14 Nov 2026)
- CISA SSVC
- Exploitation: none · Automatable: no · Technical impact: total
The list uses the assigner's score when there is one, then CISA's, then NVD's: High 8.8.
Affected products
- affected d38ceaf99ed015f2a0b9af3499791bd3a3daae21 – < 40df11255d71b02e20e70579f1b12b687e396e26
- affected d38ceaf99ed015f2a0b9af3499791bd3a3daae21 – < 91fbb5e635c8fb1b49e15c19da06480089ef719f
- affected d38ceaf99ed015f2a0b9af3499791bd3a3daae21 – < 8ae8b9e74bab94aab1d79f1688129bcc61c8b29a
- affected d38ceaf99ed015f2a0b9af3499791bd3a3daae21 – < b17175d0a375b3ed5e81597dac4983fdb46e478d
- affected d38ceaf99ed015f2a0b9af3499791bd3a3daae21 – < 791941be5da125d9a1b228582bfdc300c05d05b3
- affected d38ceaf99ed015f2a0b9af3499791bd3a3daae21 – < e6c2e6c2e1fa066968a16aca1cb66cd1bdde7741
- affected 4.2
- unaffected < 4.2
- unaffected 6.1.175 – ≤ 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
- https://git.kernel.org/stable/c/40df11255d71b02e20e70579f1b12b687e396e26 (opens in a new tab)
- https://git.kernel.org/stable/c/91fbb5e635c8fb1b49e15c19da06480089ef719f (opens in a new tab)
- https://git.kernel.org/stable/c/8ae8b9e74bab94aab1d79f1688129bcc61c8b29a (opens in a new tab)
- https://git.kernel.org/stable/c/b17175d0a375b3ed5e81597dac4983fdb46e478d (opens in a new tab)
- https://git.kernel.org/stable/c/791941be5da125d9a1b228582bfdc300c05d05b3 (opens in a new tab)
- https://git.kernel.org/stable/c/e6c2e6c2e1fa066968a16aca1cb66cd1bdde7741 (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2026-45447 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2026-53374)Record last updated .