# CVE-2026-89808: drm/amdkfd: Fix the case that vm range is hole at svm_migrate_copy_to_vram

> A flaw in the Linux kernel's AMD GPU driver allows a local attacker to cause a denial of service by triggering an uninitialized variable usage during memory migration.

- **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-101415, BELL-CVE-2026-89808, DEBIAN-CVE-2026-89808, GHSA-r66w-v4mr-3pxg, UBUNTU-CVE-2026-89808

## What is CVE-2026-89808?

CVE-2026-89808 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 the case that vm range is hole at svm_migrate_copy_to_vram

When migration vm range is hole at cpu side(MIGRATE_PFN_MIGRATE set +
MIGRATE_PFN_VALID unset) driver still allocates device pages. There is no
dma map of src pages and migration. j is 0 and svm_migrate_copy_memory_gart()
will return an uninitialized r. That can trigger out_free_vram_pages to drop
all VRAM just set up.

Initialize r and only call the last svm_migrate_copy_memory_gart if j > 0.

Current code postponed the last page to the final copy. This patch flushes on
the last page when reach to the end of current drm_buddy_block; avoids another
svm_migrate_copy_memory_gart.

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


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

Apply the vendor's patch.

## Is CVE-2026-89808 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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