In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu: zero-initialize GART table on allocation GART TLB is flushed after… (CVE-2026-53374)
A vulnerability in the Linux kernel's AMDGPU driver was resolved by zero-initializing the GART table upon allocation. The issue involved the GART TLB being flushed after unmapping but not after mapping, allowing speculative loading of uninitialized entries that could cause the GPU to use stale or garbage page table entries. The fix involves zero-initializing the GART table immediately after allocation to prevent this behavior.
AI Analysis
Technical Summary
The Linux kernel AMDGPU driver had a vulnerability where the Graphics Address Remapping Table (GART) Translation Lookaside Buffer (TLB) was flushed after unmapping but not after mapping. Because the buffer was not zero-initialized on creation, speculative execution could cause the TLB to load uninitialized entries from the same cacheline, which might appear valid. Subsequent writes could cause the GPU to use stale or garbage page table entries, potentially leading to incorrect GPU memory mappings. The vulnerability was fixed by calling memset_io() to zero-initialize the GART table with appropriate flags immediately after allocation.
Potential Impact
This vulnerability could lead to the GPU using stale or garbage page table entries due to speculative loading of uninitialized GART entries. This may cause incorrect GPU memory mappings, potentially affecting GPU operation or stability. No known exploits in the wild have been reported. The impact is limited to systems using the AMDGPU driver in the Linux kernel.
Mitigation Recommendations
A fix has been implemented in the Linux kernel by zero-initializing the GART table immediately after allocation. Users should apply the official Linux kernel updates that include this patch. Since this is a kernel-level fix, updating to a kernel version containing the patch is the recommended remediation. Patch status is confirmed resolved by the commit referenced in the description.
In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu: zero-initialize GART table on allocation GART TLB is flushed after… (CVE-2026-53374)
Description
A vulnerability in the Linux kernel's AMDGPU driver was resolved by zero-initializing the GART table upon allocation. The issue involved the GART TLB being flushed after unmapping but not after mapping, allowing speculative loading of uninitialized entries that could cause the GPU to use stale or garbage page table entries. The fix involves zero-initializing the GART table immediately after allocation to prevent this behavior.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The Linux kernel AMDGPU driver had a vulnerability where the Graphics Address Remapping Table (GART) Translation Lookaside Buffer (TLB) was flushed after unmapping but not after mapping. Because the buffer was not zero-initialized on creation, speculative execution could cause the TLB to load uninitialized entries from the same cacheline, which might appear valid. Subsequent writes could cause the GPU to use stale or garbage page table entries, potentially leading to incorrect GPU memory mappings. The vulnerability was fixed by calling memset_io() to zero-initialize the GART table with appropriate flags immediately after allocation.
Potential Impact
This vulnerability could lead to the GPU using stale or garbage page table entries due to speculative loading of uninitialized GART entries. This may cause incorrect GPU memory mappings, potentially affecting GPU operation or stability. No known exploits in the wild have been reported. The impact is limited to systems using the AMDGPU driver in the Linux kernel.
Mitigation Recommendations
A fix has been implemented in the Linux kernel by zero-initializing the GART table immediately after allocation. Users should apply the official Linux kernel updates that include this patch. Since this is a kernel-level fix, updating to a kernel version containing the patch is the recommended remediation. Patch status is confirmed resolved by the commit referenced in the description.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-45w5-677j-gmrq
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-53374"]
- Ecosystems
- []
- Database Specific Severity
- null
- Cvss Version
- null
Threat ID: 6a5d27ae2a4a8d59891328ba
Added to database: 07/19/2026, 19:38:22 UTC
Last enriched: 07/19/2026, 20:25:28 UTC
Last updated: 07/20/2026, 17:26:47 UTC
Views: 16
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.