dbcve.org
Linux KernelOperating system · Linux

CVE-2026-53374

HIGH · 8.8 CVSS v3.1 Published 2026-07-19
Fix available
A fix is available. Upgrade to 6.1.175 / 6.6.140 or later.
See remediation →
90/100
Remediation priority · Urgent
Zero-click 4 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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)

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

In the Linux kernel's amdgpu driver, the amdgpu_bo_create_kernel() function fails to zero-initialize the GART (Graphics Address Remapping Table) buffer after allocation. When a single PTE is written, the TLB can speculatively load uninitialized entries from the same CPU cacheline, causing garbage PTE values to appear valid. A subsequent write to another PTE in that cacheline can cause the GPU to use stale garbage PTEs from the TLB, potentially leading to memory corruption or information disclosure.

MitigationApply the kernel patch which adds memset_io() to zero-initialize the GART table immediately after allocation, ensuring all PTEs are cleared before use. This is a driver-level fix requiring kernel source modification.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Linux KernelOperating system
Affected:>= 4.2, < 6.1.175>= 6.2, < 6.6.140>= 6.7, < 6.12.90>= 6.13, < 6.18.32>= 6.19, < 7.0.9= 7.1

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check kernel version against affected ranges
    Run 'uname -r' or 'cat /proc/version' to obtain the running kernel version
    Affected if The kernel version falls within any of these ranges: >= 4.2 and < 6.1.175, >= 6.2 and < 6.6.140, >= 6.7 and < 6.12.90, >= 6.13 and < 6.18.32, >= 6.19 and < 7.0.9, or equals 7.1
  2. Verify AMDGPU driver is loaded
    Run 'lsmod | grep amdgpu' or check if '/sys/module/amdgpu' exists
    Affected if The amdgpu kernel module is loaded or the module directory exists
  3. Confirm AMD GPU hardware is present
    Run 'lspci | grep -i amd' or 'lspci | grep -i radeon' to list AMD graphics devices
    Affected if AMD GPU hardware is detected that uses the amdgpu driver
  4. Check for patched function behavior
    Inspect the amdgpu_bo_create_kernel function in the kernel source or vmlinux for the presence of memset_io or similar zero-initialization of GART table buffers
    Affected if The function lacks zero-initialization code for GART table buffers (the vulnerability is unpatched)

You are affected if your kernel version is in the affected ranges AND the amdgpu driver is loaded AND you have AMD GPU hardware AND the vulnerability is not patched in your kernel.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Upgrade available Upgrade to 6.1.175 / 6.6.140 / 6.12.90 or later
Fixed in 6.1.1756.6.1406.12.90
Interim mitigation

Apply the kernel patch which adds memset_io() to zero-initialize the GART table immediately after allocation, ensuring all PTEs are cleared before use. This is a driver-level fix requiring kernel source modification.

Fix this in Linux Kernel Scoped from the published advisory
  • Consultation4.0 h
  • Implementation3.0 h
  • Testing12.0 h
  • Review / QA5.0 h
24.0 hours of engineering $4,040
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,464.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-53374 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-53374 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data