All reports
Medium

kernel: drm/amdkfd: Fix error path at svm_migrate_copy_to_ram

Affected versions

Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported

Exploitation

CVE-2026-89810

Probability of exploitation in the next 30 days: 0.18%

FIRST EPSS · 2026-11-17

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.

A flaw was found in the Linux kernel's drm/amdkfd component. When page migration from a device to system RAM fails, the driver incorrectly uses a DMA (Direct Memory Access) address instead of a physical address to release and unlock allocated system pages. This improper handling of memory resources, especially when an IOMMU (Input/Output Memory Management Unit) is enabled, can lead to system instability or resource exhaustion.