# CVE-2026-89812: drm/amdgpu: force complete the MES ring fences on reset

> A flaw in the Linux kernel amdgpu driver causes a denial of service by wedging the GPU during reset due to unsynchronized MES ring fences.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 16 Sep 2026
- **Updated:** 21 Oct 2026
- **Also known as:** AZL-101312, BELL-CVE-2026-89812, DEBIAN-CVE-2026-89812, GHSA-45jc-gxg9-3gvc, UBUNTU-CVE-2026-89812

## What is CVE-2026-89812?

CVE-2026-89812 is a denial of service vulnerability in Linux, published on 16 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: force complete the MES ring fences on reset

The MES scheduler ring has no drm scheduler (no_scheduler = true), so it is
skipped by the force-completion loop in amdgpu_device_pre_asic_reset(). It uses
a polling fence whose hw value lives in wb (GTT) memory and survives a MODE1
reset, while fence_drv.sync_seq keeps advancing for every packet.

When the reset is triggered because MES itself stopped responding, the
timed-out packets advance sync_seq past the last hw fence value MES wrote.
After resume the first MES submission polls forever on a seq that is never
written back, failing the resume and wedging the box on a second reset:

  amdgpu: MES ring buffer is full.
  amdgpu: *ERROR* ring gfx_0.0.0 test failed (-110)
  amdgpu: resume of IP block <gfx_v11_0> failed -110
  amdgpu: GPU reset end with ret = -110

Force complete the MES scheduler ring fences together with the scheduler rings
so their hw fence is realigned to sync_seq.

v2: cover all XCCs (one scheduler ring each), not just mes.ring[0].

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


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

Apply the vendor's patch.

## Is CVE-2026-89812 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-89812 is a denial of service vulnerability in Linux, published on 16 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-89812 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-89812/ (Markdown: https://insights.sbomify.com/CVE-2026-89812/index.md)
```

## Sources

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

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