SECUFOCUSNOW
Home›CVE index›CVE-2026-53374
Review reviewHigh

CVE-2026-53374

Linux Linux, linux kernel

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_...

CVSS
8.8
EPSS
0.12%
2.18% percentile
CISA KEV
Not listed
Published
2026.07.19
PRIORITY ASSESSMENT

Review review

The CVSS severity warrants an early asset and exposure review.

Known exploitationNot established by KEV
Exploit probability0.12%
Technical severityCVSS 8.8

Vulnerability overview

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_...

Affected product and versions

Product
Linux Linux, linux kernel
Affected versions
>= d38ceaf99ed015f2a0b9af3499791bd3a3daae21 < 40df11255d71b02e20e70579f1b12b687e396e26, >= d38ceaf99ed015f2a0b9af3499791bd3a3daae21 < 91fbb5e635c8fb1b49e15c19da06480089ef719f, >= d38ceaf99ed015f2a0b9af3499791bd3a3daae21 < 8ae8b9e74bab94aab1d79f1688129bcc61c8b29a, >= d38ceaf99ed015f2a0b9af3499791bd3a3daae21 < b17175d0a375b3ed5e81597dac4983fdb46e478d, >= d38ceaf99ed015f2a0b9af3499791bd3a3daae21 < 791941be5da125d9a1b228582bfdc300c05d05b3, >= d38ceaf99ed015f2a0b9af3499791bd3a3daae21 < e6c2e6c2e1fa066968a16aca1cb66cd1bdde7741, >= 4.2, >= 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
Fixed versions
6.1.175, 6.6.140, 6.12.90, 6.18.32, 7.0.9

Recommended response sequence

Confirm exposure before applying a vendor-supported change.

Full remediation guide
  1. 1
    Identify

    Confirm that Linux Linux, linux kernel and an affected version are present.

  2. 2
    Prioritize

    Combine exploitation signals with asset exposure and business criticality.

  3. 3
    Remediate

    Follow the vendor advisory or supported update path and preserve rollback options.

  4. 4
    Verify

    Recheck the version, service health, access paths, and relevant logs.

Technical data

CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
CWE
Not available