Look up another CVE · open CVE-2026-89808 in the interactive tracker
CVE-2026-89808
drm/amdkfd: Fix the case that vm range is hole at svm_migrate_copy_to_vram
Published 2026-09-16 (33 days ago) by the Linux kernel CNA. Subsystem drivers/gpu. Debian urgency: not yet assigned.
What to do, per Debian release
Debian's own status for CVE-2026-89808 in every release this site tracks, and what each one means in practice. Every status below is the one the Debian Security Team publishes for this CVE. source
| Release | Status | Version | What this means |
|---|---|---|---|
| Debian 12bookworm | vulnerable | 6.1.190-1 | No fix published anywhere yet, neither in Debian nor upstream for the series bookworm tracks. Watch the Debian tracker page for this CVE. Advisories for bookworm have historically landed a median of 23 days after publication. |
| Debian 13trixie | vulnerable | 6.12.113-1 | No fix published anywhere yet, neither in Debian nor upstream for the series trixie tracks. Watch the Debian tracker page for this CVE. Advisories for trixie have historically landed a median of 11 days after publication. |
| Debian 14forky | fixed | 7.2.6-1 | Update the kernel and reboot. Fixed in 7.2.6-1. A running kernel keeps the old code until the machine restarts. |
| Debian unstablesid | fixed | 7.2.6-1 | Update the kernel and reboot. Fixed in 7.2.6-1. A running kernel keeps the old code until the machine restarts. |
The vulnerability
What the bug is
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.
Where it lives
The fix touches these files. If the subsystem is one you do not use, the practical exposure is lower, though the package is still the vulnerable one.
drivers/gpu/drm/amd/amdkfd/kfd_migrate.c
- What this is
- AMD KFDMAINTAINERS section matched on drivers/gpu/drm/amd/amdkfd/ · amd-gfx@lists.freedesktop.org · Supported
Show whether Debian builds this, per release
Not established. This site could not find the build rule for the affected file in the kernel trees Debian ships, so it has no answer about whether Debian compiles this code. Read that as unknown, never as absent.
- bookworm, trixie, forky, sid?
- ?
- not established - no Makefile entry for the affected file
Where a release above reads "not established", no build rule for the affected file was found in that release's kernel tree. That is a gap in this lookup, not a finding that the code is absent.
From the configuration Debian publishes for every kernel flavour it builds. It covers only the architectures Debian ships a linux-config package for, and nothing about a kernel you built yourself. Debian's own status above stays authoritative about the source package.MAINTAINERS
Signals
- Published
- 2026-09-16 (33 days ago)source
- CVSS
- 7.8 high
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:Hsource recompute it - Attack vector
- local (AV:L)source
- EPSS
- 0.17%, higher than 6.3% of all CVEssource
- CISA KEV
- not listedthe KEV catalogue
- Debian urgency
- not yet assignedsource
- Subsystem
- drivers/gpu
Upstream fixes
The versions the CNA records as introducing and fixing this, and the commit for each. source
| Introduced | Fixed in | Commit |
|---|---|---|
| 5.14 | 6.18.51 | ae806a95b28f |
| 5.14 | 7.2.5 | 0a9a0e8a97da |
| 5.14 | 7.3 | 520e345ffe05 |
Why the CNA scored it this way
Quoted from the kernel CNA's own scoring file, word for word. A highlighted metric carries the most severe value CVSS v3.1 defines for it, which is what pushes the score up. source
- AV:LAttack vector, local
- The bug is reached only via local /dev/kfd AMDKFD_IOC_SVM (SET_ATTR prefetch) or the process's own GPU page-fault SVM restore into svm_migrate_copy_to_vram; it is not reachable from network packets, adjacent wireless, or a physical bus.
- AC:LAttack complexity, low
- An attacker creates anonymous VMA holes (untouched mmap or zero pages) and triggers migration with AMDKFD_IOC_SVM PREFETCH_LOC; migrate_vma records MIGRATE_PFN_MIGRATE without VALID so j stays 0 and the uninitialized-r path runs with no race, victim state, or rare config (HSA_AMD_SVM defaults y).
- PR:LPrivileges required, low
- kfd_open() and AMDKFD_IOC_SVM perform no capable() checks (ioctl flag 0, unlike CRIU); /dev/kfd and the DRM render node are available to unprivileged render-group users on typical ROCm, desktop, and Android AMD GPU systems, which is Low privilege not init-namespace root.
- UI:NUser interaction, none
- Exploitation uses only the attacker's own /dev/kfd file descriptor, anonymous mappings, and SVM ioctls; no separate victim must mount a filesystem, open a file, or take any other action.
- S:UScope, unchanged
- Impact is confined to amdkfd SVM/GPUVM state and ZONE_DEVICE pages in the host kernel; it does not cross a VM, hypervisor, IOMMU device-isolation, or sandbox security authority.
- C:HConfidentiality impact, high
- Spurious out_free_vram_pages unlocks and puts destination ZONE_DEVICE pages (page_free → svm_range_bo_unref_async) while SDMA may still copy into that VRAM and a non-zero leftover r can still mark the range GPU-resident; that device-page UAF enables kernel/VRAM disclosure.
- I:HIntegrity impact, high
- The same premature free of migrate destination pages, while actual_loc/vram_pages may still record a successful GPU migration, lets later HMM/GPUVM/SDMA operate on put ZONE_DEVICE pages and svm_bo refs, a kernel UAF write/control-flow primitive scored High per UAF guidance.
- A:HAvailability impact, high
- Putting still-in-use ZONE_DEVICE pages and leaving SVM actual_loc/vram_pages inconsistent reliably causes kernel oops/WARN (bad page lock, folio_put on freed pages, VRAM BO validation) or GPU hang/reset, which is High availability impact.