Skip to main content
VulnerabilityPublished Updated

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

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-89808· High 7.8

Not known to be exploited · CVSS 7.8 High · fixed in d5872c81c70163a3ba9eb4da9a94c92b03067576 : patch Linux kernel soon.

Data as of 30 Oct 2026, 16:33 UTC

CVSS 3.1 base score
7.8High
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (Linux)CVSS 3.17.8
Patch
Available – fixed in d5872c81c70163a3ba9eb4da9a94c92b03067576, bd1adb2e5101db649121b59e601c92773a302a70, ae806a95b28fcecb913430cfa45a252e91a945d6 +3
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 16 Sep 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ 50ea50cf6f6d31d3235ad1853c5dbea766a3ed11, < d5872c81c70163a3ba9eb4da9a94c92b03067576
Fixed in
  • d5872c81c70163a3ba9eb4da9a94c92b03067576
LinuxLinuxAffected
  • ≥ 50ea50cf6f6d31d3235ad1853c5dbea766a3ed11, < bd1adb2e5101db649121b59e601c92773a302a70
Fixed in
  • bd1adb2e5101db649121b59e601c92773a302a70
LinuxLinuxAffected
  • ≥ 50ea50cf6f6d31d3235ad1853c5dbea766a3ed11, < ae806a95b28fcecb913430cfa45a252e91a945d6
Fixed in
  • ae806a95b28fcecb913430cfa45a252e91a945d6
LinuxLinuxAffected
  • ≥ 50ea50cf6f6d31d3235ad1853c5dbea766a3ed11, < 520e345ffe05aabef1db82beda4288afb1757ff2
Fixed in
  • 520e345ffe05aabef1db82beda4288afb1757ff2
LinuxLinuxAffected
  • ≥ 50ea50cf6f6d31d3235ad1853c5dbea766a3ed11, < 6e1a6f3ddb87d7f89a775c55fb399680c02bdcc2
Fixed in
  • 6e1a6f3ddb87d7f89a775c55fb399680c02bdcc2
LinuxLinuxAffected
  • ≥ 50ea50cf6f6d31d3235ad1853c5dbea766a3ed11, < 0a9a0e8a97da70a0336c9115178aaf1be29bcfb1
Fixed in
  • 0a9a0e8a97da70a0336c9115178aaf1be29bcfb1

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.

References

Community reviews

Loading reviews…