Skip to content
Hardware

CVE-2026-53374

8.8
High
EPSS 0.13%Patch availableJul 21, 2026

Linux amdgpu GART not zeroed allows stale PTEs, causing GPU memory corruption.

common questions

Is CVE-2026-53374 being exploited?

Not confirmed. CVE-2026-53374 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.13% probability of exploitation in the next 30 days.

How severe is CVE-2026-53374?

CVE-2026-53374 is rated High with a CVSS score of 8.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-53374?

Yes. A fix has been recorded for CVE-2026-53374. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-53374 affect?

CVE-2026-53374 affects Linux kernel (drm/amdgpu), Systems with AMD GPUs, Distributions with amdgpu enabled, Containers/VMs exposing GPU devices. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-53374?

Update Linux kernel to the patched amdgpu release and restrict GPU device access until patched.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
Linux kernel (drm/amdgpu)Systems with AMD GPUsDistributions with amdgpu enabledContainers/VMs exposing GPU devices
impact

Local attacker with GPU access can trigger stale GART PTEs, causing GPU memory corruption, possible data disclosure or local privilege escalation.

action required

Patch when possible

affected versions
Linux Linux
  • affected>= d38ceaf99ed015f2a0b9af3499791bd3a3daae21 and < 40df11255d71b02e20e70579f1b12b687e396e26
  • affected>= d38ceaf99ed015f2a0b9af3499791bd3a3daae21 and < 91fbb5e635c8fb1b49e15c19da06480089ef719f
  • affected>= d38ceaf99ed015f2a0b9af3499791bd3a3daae21 and < 8ae8b9e74bab94aab1d79f1688129bcc61c8b29a
  • affected>= d38ceaf99ed015f2a0b9af3499791bd3a3daae21 and < b17175d0a375b3ed5e81597dac4983fdb46e478d
  • affected>= d38ceaf99ed015f2a0b9af3499791bd3a3daae21 and < 791941be5da125d9a1b228582bfdc300c05d05b3
  • affected>= d38ceaf99ed015f2a0b9af3499791bd3a3daae21 and < e6c2e6c2e1fa066968a16aca1cb66cd1bdde7741
  • affected4.2
vendor says fixed in< 4.2, >= 6.1.175 and <= 6.1.*, >= 6.6.140 and <= 6.6.*, >= 6.12.90 and <= 6.12.*, >= 6.18.32 and <= 6.18.*, >= 7.0.9 and <= 7.0.*, >= 7.1 and <= *

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free