drm/amdgpu/gfx6: Use PFP on the compute queues too
- 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 5.10.270, 5.15.221, 6.1.188, 6.6.157, 6.12.110, and 2 more
- 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
Summary
In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu/gfx6: Use PFP on the compute queues too On GFX6, the compute rings use the same CP path as the graphics ring. The only difference is that they don't support draw commands. (As opposed to GFX7 and newer which have a separate command parser that is called MEC for compute queues.) This means that we have to take into consideration that the PFP also exists on compute queues on GFX6: Use PFP for register writes on both graphics and compute queues. In the pipeline sync, use the PFP to wait for the previous fence (and not the ME) to prevent the PFP from starting to execute the next submission while the ME is still in the previous submission. After a VM flush, emit PFP_SYNC_ME on compute queues as well.
Timeline
- CVE published
- Record last updated
Affected versions
- Linux Linux
From 2cd46ad22383ab8372b86cdb5257589496099412 · fixed in f37211b9c01433f0bbb4709d25df7a0257cf915b; From 2cd46ad22383ab8372b86cdb5257589496099412 · fixed in 2aa869c6b23e0b1b7f39f762618852811d75deb9; From 2cd46ad22383ab8372b86cdb5257589496099412 · fixed in fbabc39b4f0fc771b00525ffd448be6a84355048; From 2cd46ad22383ab8372b86cdb5257589496099412 · fixed in b5d1d3e4519dc8f1b55d6b236848bed67b11a2e8; From 2cd46ad22383ab8372b86cdb5257589496099412 · fixed in e1d3018e3621c90cec070b6915836ae129656663; From 2cd46ad22383ab8372b86cdb5257589496099412 · fixed in 8d752f1bb73fabe5a425acbf5c767c0fe68bf3c5; From 2cd46ad22383ab8372b86cdb5257589496099412 · fixed in e399e9d7e291ccbeba6560fb8278c8d2aa744521; From 2cd46ad22383ab8372b86cdb5257589496099412 · fixed in 60f20946cd318518ddc2c0da12103c666b2b9564
- Linux Linux
4.9
- KernelLinux
From 4.9.0 · fixed in 5.10.270; From 5.11.0 · fixed in 5.15.221; From 5.16.0 · fixed in 6.1.188; From 6.2.0 · fixed in 6.6.157; From 6.7.0 · fixed in 6.12.110; From 6.13.0 · fixed in 6.18.52; From 6.19.0 · fixed in 7.2.6
References 8
git.kernel.org
- stable/c/f37211b9c01433f0bbb4709d25df7a0257cf915b
- stable/c/2aa869c6b23e0b1b7f39f762618852811d75deb9
- stable/c/fbabc39b4f0fc771b00525ffd448be6a84355048
- stable/c/b5d1d3e4519dc8f1b55d6b236848bed67b11a2e8
- stable/c/e1d3018e3621c90cec070b6915836ae129656663
- stable/c/8d752f1bb73fabe5a425acbf5c767c0fe68bf3c5
- stable/c/e399e9d7e291ccbeba6560fb8278c8d2aa744521
- stable/c/60f20946cd318518ddc2c0da12103c666b2b9564