CVE-2026-53374
CVE.org · Published
- Record status
- Published
- Identifier year (not publication year)
- 2026
- Source publication
- Source updated
- Imported by cveboard
- Source snapshot
- cve_2026-10-24_midnight_baseline ·
CNA source text (English)
drm/amdgpu: zero-initialize GART table on allocation
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)
Scoped product and version facts
Fix information unknown; no fixed version is derived here. Missing information does not prove that no fix exists.
Exploitation unknown; this catalogue does not assess exploitation.
Linux
- Vendor
- Linux
- Product
- Linux
- Platforms
- Unknown
- Default status
unaffected
| Version (version) | Status (status) | Version scheme (versionType) | Exclusive end (lessThan) | Inclusive end (lessThanOrEqual) | Status changes (at → status) |
|---|---|---|---|---|---|
| d38ceaf99ed015f2a0b9af3499791bd3a3daae21 | affected | git | 40df11255d71b02e20e70579f1b12b687e396e26 | Unavailable | None listed |
| d38ceaf99ed015f2a0b9af3499791bd3a3daae21 | affected | git | 91fbb5e635c8fb1b49e15c19da06480089ef719f | Unavailable | None listed |
| d38ceaf99ed015f2a0b9af3499791bd3a3daae21 | affected | git | 8ae8b9e74bab94aab1d79f1688129bcc61c8b29a | Unavailable | None listed |
| d38ceaf99ed015f2a0b9af3499791bd3a3daae21 | affected | git | b17175d0a375b3ed5e81597dac4983fdb46e478d | Unavailable | None listed |
| d38ceaf99ed015f2a0b9af3499791bd3a3daae21 | affected | git | 791941be5da125d9a1b228582bfdc300c05d05b3 | Unavailable | None listed |
| d38ceaf99ed015f2a0b9af3499791bd3a3daae21 | affected | git | e6c2e6c2e1fa066968a16aca1cb66cd1bdde7741 | Unavailable | None listed |
Linux
- Vendor
- Linux
- Product
- Linux
- Platforms
- Unknown
- Default status
affected
| Version (version) | Status (status) | Version scheme (versionType) | Exclusive end (lessThan) | Inclusive end (lessThanOrEqual) | Status changes (at → status) |
|---|---|---|---|---|---|
| 4.2 | affected | Unavailable | Unavailable | Unavailable | None listed |
| 0 | unaffected | semver | 4.2 | Unavailable | None listed |
| 6.1.175 | unaffected | semver | Unavailable | 6.1.* | None listed |
| 6.6.140 | unaffected | semver | Unavailable | 6.6.* | None listed |
| 6.12.90 | unaffected | semver | Unavailable | 6.12.* | None listed |
| 6.18.32 | unaffected | semver | Unavailable | 6.18.* | None listed |
| 7.0.9 | unaffected | semver | Unavailable | 7.0.* | None listed |
| 7.1 | unaffected | original_commit_for_fix | Unavailable | * | None listed |