CVE-2026-90286drm/amdgpu/gfx6: Use PFP on the compute queues too
- 8.8HighCVSS base score
- 0.18%Exploitation in 30 daysEPSS · top 93% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
Description
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
ID reserved
By Linux
- 6 days later
· 6 days later
Published
- 32 days later
· 32 days later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| LinuxCNA (assigner) | 3.1 | High8.8 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H |
| NVDNVD · Received | 3.1 | High8.8 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H |
- EPSS (exploitation in 30 days)
- 0.18% · top 93% of all CVEs (14 Nov 2026)
The list uses the assigner's score when there is one, then CISA's, then NVD's: High 8.8.
Affected products
- affected 2cd46ad22383ab8372b86cdb5257589496099412 – < f37211b9c01433f0bbb4709d25df7a0257cf915b
- affected 2cd46ad22383ab8372b86cdb5257589496099412 – < 2aa869c6b23e0b1b7f39f762618852811d75deb9
- affected 2cd46ad22383ab8372b86cdb5257589496099412 – < fbabc39b4f0fc771b00525ffd448be6a84355048
- affected 2cd46ad22383ab8372b86cdb5257589496099412 – < b5d1d3e4519dc8f1b55d6b236848bed67b11a2e8
- affected 2cd46ad22383ab8372b86cdb5257589496099412 – < e1d3018e3621c90cec070b6915836ae129656663
- affected 2cd46ad22383ab8372b86cdb5257589496099412 – < 8d752f1bb73fabe5a425acbf5c767c0fe68bf3c5
- affected 2cd46ad22383ab8372b86cdb5257589496099412 – < e399e9d7e291ccbeba6560fb8278c8d2aa744521
- affected 2cd46ad22383ab8372b86cdb5257589496099412 – < 60f20946cd318518ddc2c0da12103c666b2b9564
- affected 4.9
- unaffected < 4.9
- unaffected 5.10.270 – ≤ 5.10.*
- unaffected 5.15.221 – ≤ 5.15.*
- unaffected 6.1.188 – ≤ 6.1.*
- unaffected 6.6.157 – ≤ 6.6.*
- unaffected 6.12.110 – ≤ 6.12.*
- unaffected 6.18.52 – ≤ 6.18.*
- unaffected 7.2.6 – ≤ 7.2.*
- unaffected 7.3 – ≤ *
References
References8
- https://git.kernel.org/stable/c/f37211b9c01433f0bbb4709d25df7a0257cf915b (opens in a new tab)
- https://git.kernel.org/stable/c/2aa869c6b23e0b1b7f39f762618852811d75deb9 (opens in a new tab)
- https://git.kernel.org/stable/c/fbabc39b4f0fc771b00525ffd448be6a84355048 (opens in a new tab)
- https://git.kernel.org/stable/c/b5d1d3e4519dc8f1b55d6b236848bed67b11a2e8 (opens in a new tab)
- https://git.kernel.org/stable/c/e1d3018e3621c90cec070b6915836ae129656663 (opens in a new tab)
- https://git.kernel.org/stable/c/8d752f1bb73fabe5a425acbf5c767c0fe68bf3c5 (opens in a new tab)
- https://git.kernel.org/stable/c/e399e9d7e291ccbeba6560fb8278c8d2aa744521 (opens in a new tab)
- https://git.kernel.org/stable/c/60f20946cd318518ddc2c0da12103c666b2b9564 (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2026-81879 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2026-90286)Record last updated .