# CVE-2026-89810: drm/amdkfd: Fix error path at svm_migrate_copy_to_ram

> A bug in the AMD KFD driver's error handling path can lead to resource leaks or instability when page migration fails, potentially causing denial of service.

- **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:** 21 Oct 2026
- **Also known as:** AZL-101484, BELL-CVE-2026-89810, DEBIAN-CVE-2026-89810, GHSA-xrq7-rc4j-2cmm, UBUNTU-CVE-2026-89810

## What is CVE-2026-89810?

CVE-2026-89810 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/amdkfd: Fix error path at svm_migrate_copy_to_ram

If page migration from device to sys ram fails for some reasons driver needs
release and unlock allocated system pages. To do that driver should use page
physical address, or pfn, then get struct page*. Current driver uses dma
address(for adev) that is not correct with IOMMU enabled, or even in general.

The patch releases and unlocks allocated system pages based on where migration
failed by struct page* of sys ram pages. Also dma_unmap correspodent system
ram pages at error path.

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


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

Apply the vendor's patch.

## Is CVE-2026-89810 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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