# CVE-2026-89813: drm/amdgpu: force complete the KIQ ring fences on reset

> A flaw in the Linux kernel's amdgpu driver causes a denial of service during GPU reset due to incomplete fence handling.

- **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-101316, BELL-CVE-2026-89813, DEBIAN-CVE-2026-89813, GHSA-r5wm-5xw8-prj5, UBUNTU-CVE-2026-89813

## What is CVE-2026-89813?

CVE-2026-89813 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 KIQ ring fences on reset

Like the MES scheduler ring, the KIQ ring sets no_scheduler = true and uses a
polling fence, so it is skipped by the force-completion loop in
amdgpu_device_pre_asic_reset(). Its hw fence value lives in wb (GTT) memory and
survives a MODE1 reset while fence_drv.sync_seq keeps advancing, so after a
reset the first KIQ submission can poll forever on a seq that is never written
back.

Force complete the KIQ ring fences too so their hw fence is realigned to
sync_seq.

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


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

Apply the vendor's patch.

## Is CVE-2026-89813 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-89813 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-89813 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-89813/ (Markdown: https://insights.sbomify.com/CVE-2026-89813/index.md)
```

## Sources

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

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