---
title: "CVE-2026-90286: CVE-2026-90286"
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."
url: https://panop.io/threat-heartbeat/CVE-2026-90286/
---

# CVE-2026-90286 CVE-2026-90286

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.

CVSS base score 8.8 /10

High

CISA KEV

Not listed

Public exploit

None known

EPSS

0.18% chance of exploitation in 30 days

[View the NVD record ↗](https://nvd.nist.gov/vuln/detail/CVE-2026-90286)

## Details

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H

Published

17 September 2026

Updated

15 October 2026

## References

- [https://nvd.nist.gov/vuln/detail/CVE-2026-90286](https://nvd.nist.gov/vuln/detail/CVE-2026-90286)
- [https://git.kernel.org/stable/c/f37211b9c01433f0bbb4709d25df7a0257cf915b](https://git.kernel.org/stable/c/f37211b9c01433f0bbb4709d25df7a0257cf915b)
- [https://git.kernel.org/stable/c/fbabc39b4f0fc771b00525ffd448be6a84355048](https://git.kernel.org/stable/c/fbabc39b4f0fc771b00525ffd448be6a84355048)
- [https://git.kernel.org/stable/c/2aa869c6b23e0b1b7f39f762618852811d75deb9](https://git.kernel.org/stable/c/2aa869c6b23e0b1b7f39f762618852811d75deb9)
- [https://git.kernel.org/stable/c/60f20946cd318518ddc2c0da12103c666b2b9564](https://git.kernel.org/stable/c/60f20946cd318518ddc2c0da12103c666b2b9564)
- [https://git.kernel.org/stable/c/8d752f1bb73fabe5a425acbf5c767c0fe68bf3c5](https://git.kernel.org/stable/c/8d752f1bb73fabe5a425acbf5c767c0fe68bf3c5)
- [https://git.kernel.org/stable/c/b5d1d3e4519dc8f1b55d6b236848bed67b11a2e8](https://git.kernel.org/stable/c/b5d1d3e4519dc8f1b55d6b236848bed67b11a2e8)
- [https://git.kernel.org/stable/c/e1d3018e3621c90cec070b6915836ae129656663](https://git.kernel.org/stable/c/e1d3018e3621c90cec070b6915836ae129656663)
- [https://git.kernel.org/stable/c/e399e9d7e291ccbeba6560fb8278c8d2aa744521](https://git.kernel.org/stable/c/e399e9d7e291ccbeba6560fb8278c8d2aa744521)

[← All CVEs](https://panop.io/threat-heartbeat/)

## What this record can't tell you

- Whether you run the affected software, and where
- Whether an attacker can actually reach and exploit it
- The misconfigurations that never get a CVE number
- What it would cost the business, ranked into what to fix first

Panop answers these inside your environment, for this CVE and every other finding.

[Book a demo](https://panop.io/demo)