CVE-2026-89810

drm/amdkfd: Fix error path at svm_migrate_copy_to_ram

CVE-2026-89810 is fixed in linux on 1 platform, first by DEBIAN-CVE-2026-89810, released September 23, 2026. It is not reported as exploited. Patch Radar priority: High.

High

CVSS

7.8

Important

Exploitation

None reported

No vendor assessment

CISA KEV

Not listed

Not in the Known Exploited Vulnerabilities catalog

EPSS

0.0018

7th percentile

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.

Where it's fixed

Product	Fixed in	Fix	Released
Linux
linux · Debian 13.5 (trixie)	6.12.115-2	DEBIAN-CVE-2026-89810	Sep 23, 2026
linux · Debian 14	7.2.6-1	DEBIAN-CVE-2026-89810	Sep 23, 2026

Details

Published
September 16, 2026
CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Vendor advisory
https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-89810

For tools and AI agents

This page as data: JSON · Markdown

Link to this page

If this page saved you time, a link to it in your ticket, advisory or write-up helps others find it.

HTML

<a href="https://patchblox.com/security/cve/CVE-2026-89810">CVE-2026-89810 on Patchblox Patch Radar</a>

Reusing the data? How to credit Patch Radar.

Is this on your machines?

Patchblox finds every install below the fixed version on Windows, macOS and Linux, and updates them through your release rings.

Get a demo

Patch Radar data is free to use with attribution. Terms and how to credit it.

Product names, logos and trademarks shown on Patch Radar belong to their respective owners. They are used only to identify the software each security fix applies to and to help readers find their platform. Their use does not imply any affiliation with, or endorsement by, those owners, and Patchblox is not affiliated with any of them.