drm/amdgpu: zero-initialize GART table on allocation
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 6.1.175, 6.6.140, 6.12.90, 6.18.32, 7.0.9
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: total
Summary
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)
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- Linux Linux
From d38ceaf99ed015f2a0b9af3499791bd3a3daae21 · fixed in 40df11255d71b02e20e70579f1b12b687e396e26; From d38ceaf99ed015f2a0b9af3499791bd3a3daae21 · fixed in 91fbb5e635c8fb1b49e15c19da06480089ef719f; From d38ceaf99ed015f2a0b9af3499791bd3a3daae21 · fixed in 8ae8b9e74bab94aab1d79f1688129bcc61c8b29a; From d38ceaf99ed015f2a0b9af3499791bd3a3daae21 · fixed in b17175d0a375b3ed5e81597dac4983fdb46e478d; From d38ceaf99ed015f2a0b9af3499791bd3a3daae21 · fixed in 791941be5da125d9a1b228582bfdc300c05d05b3; From d38ceaf99ed015f2a0b9af3499791bd3a3daae21 · fixed in e6c2e6c2e1fa066968a16aca1cb66cd1bdde7741
- Linux Linux
4.2
- KernelLinux
From 4.2.0 · fixed in 6.1.175; From 6.2.0 · fixed in 6.6.140; From 6.7.0 · fixed in 6.12.90; From 6.13.0 · fixed in 6.18.32; From 6.19.0 · fixed in 7.0.9