# CVE-2026-89827: drm/amdgpu: avoid force-completing uninitialized UVD rings

> A local attacker can cause a denial of service in the Linux kernel by triggering a null dereference in the AMD GPU driver when UVD rings are uninitialized.

- **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-101303, BELL-CVE-2026-89827, DEBIAN-CVE-2026-89827, GHSA-9r9g-2xp7-pmx6, UBUNTU-CVE-2026-89827

## What is CVE-2026-89827?

CVE-2026-89827 is a 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: avoid force-completing uninitialized UVD rings

uvd_v7_0_sw_init() does not initialize the UVD decode ring for an
SR-IOV VF. However, amdgpu_uvd_resume() unconditionally force-completes
the decode ring when restoring its fence sequence.

Skip fence completion when the fence driver is not initialized.

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


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

Apply the vendor's patch.

## Is CVE-2026-89827 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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