# CVE-2026-90286: drm/amdgpu/gfx6: Use PFP on the compute queues too

> A synchronization bug in the AMDGPU driver for GFX6 hardware could lead to undefined behavior or instability in compute queue operations.

- **Severity:** High 8.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 17 Sep 2026
- **Updated:** 19 Oct 2026
- **Also known as:** AZL-102119, BELL-CVE-2026-90286, DEBIAN-CVE-2026-90286, GHSA-v695-f62m-x7j7, UBUNTU-CVE-2026-90286

## What is CVE-2026-90286?

CVE-2026-90286 is a high-severity vulnerability in Linux, published on 17 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official 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.

## Which versions are affected by CVE-2026-90286?


## How do I fix CVE-2026-90286?

Apply the vendor's patch.

## Is CVE-2026-90286 being exploited?

There is no known exploitation of CVE-2026-90286 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-90286 and fix it if it is affected.

What it is: CVE-2026-90286 is a high-severity vulnerability in Linux, published on 17 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-90286 in the wild and no public exploit code.

Affected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-90286/ (Markdown: https://insights.sbomify.com/CVE-2026-90286/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-90286
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-90286
- OSV: https://osv.dev/vulnerability/CVE-2026-90286

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-90286/
Summaries are generated and may contain mistakes; the official description above is the record.