drm/amdgpu: zero-initialize GART table on allocation
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 40df11255d71b02e20e70579f1b12b687e396e26, Kernel 791941be5da125d9a1b228582bfdc300c05d05b3, Kernel 8ae8b9e74bab94aab1d79f1688129bcc61c8b29a and 3 more.
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)
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | =4.2, >=d38ceaf99ed015f2a0b9af3499791bd3a3daae21 <40df11255d71b02e20e70579f1b12b687e396e26, >=d38ceaf99ed015f2a0b9af3499791bd3a3daae21 <791941be5da125d9a1b228582bfdc300c05d05b3, >=d38ceaf99ed015f2a0b9af3499791bd3a3daae21 <8ae8b9e74bab94aab1d79f1688129bcc61c8b29a, >=d38ceaf99ed015f2a0b9af3499791bd3a3daae21 <91fbb5e635c8fb1b49e15c19da06480089ef719f, >=d38ceaf99ed015f2a0b9af3499791bd3a3daae21 <b17175d0a375b3ed5e81597dac4983fdb46e478d, >=d38ceaf99ed015f2a0b9af3499791bd3a3daae21 <e6c2e6c2e1fa066968a16aca1cb66cd1bdde7741 | 40df11255d71b02e20e70579f1b12b687e396e26, 791941be5da125d9a1b228582bfdc300c05d05b3, 8ae8b9e74bab94aab1d79f1688129bcc61c8b29a, 91fbb5e635c8fb1b49e15c19da06480089ef719f, b17175d0a375b3ed5e81597dac4983fdb46e478d, e6c2e6c2e1fa066968a16aca1cb66cd1bdde7741 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket