# CVE-2026-89814: drm/amdgpu: clamp the isolation index for rings outside a partition

> An out-of-bounds array access in the amdgpu driver can cause a kernel crash when SDMA submissions occur on rings outside a partition.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/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:** 16 Sep 2026
- **Updated:** 19 Oct 2026
- **Also known as:** AZL-101589, BELL-CVE-2026-89814, DEBIAN-CVE-2026-89814, GHSA-hf6p-44h5-hp6x, UBUNTU-CVE-2026-89814

## What is CVE-2026-89814?

CVE-2026-89814 is a high-severity 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: clamp the isolation index for rings outside a partition

adev->isolation[] has one slot per partition, but a ring that is not
assigned to one keeps AMDGPU_XCP_NO_PARTITION, which is ~0, so indexing
the array with it is out of bounds. SDMA submissions hit this on both
the isolation enforcement and the VM flush path and trip UBSAN.

Fall back to the first slot the way the cleaner shader path already
does, and stop taking the address before the ring type check that makes
it relevant.

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


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

Apply the vendor's patch.

## Is CVE-2026-89814 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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