CVE-2026-99148

drm/amdgpu: keep the eviction fence until the last handle is closed

  • High 7.0

Description

In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu: keep the eviction fence until the last handle is closed amdgpu_gem_object_close() detaches the user queue eviction fence from the BO before it checks bo_va->ref_count, so closing any handle of a BO removes the fence, even when the file still has another handle to the BO and the bo_va with its GPU mappings stays. The BO can then be evicted without suspending the user queues of the file, which keep accessing it through mappings that are only marked for update. Seen on navi31 with a SDMA user queue: a BO opened twice in the same file (GEM_FLINK + GEM_OPEN) loses its eviction fence when the second handle is closed (traced attach/detach of the fence): attach bo=ffff8c78a6c84c00 GEM_CLOSE handle=7 detach bo=ffff8c78a6c84c00 while handle 6 and the mapping are still in use. Only detach the fence when the last reference to the bo_va goes away, matching amdgpu_gem_object_open(), which attaches it only when the bo_va is created. With this the fence stays until the file is closed. (cherry picked from commit 8387982f03d4026b7dc11b0b5e3118298eee4d6a)

Key facts

Published
28 Oct 2026
Last changed
31 Oct 2026
Assigned by
Linux
EPSS
0.12% likely to be exploited in the next 30 days, higher than 1.897% of CVEs (scores for 16 Nov 2026)

Severity scores

Each score is shown as its source gave it. They are not averaged or merged.

  • 7.0CVSS 3.1, Highfrom the CNA (Linux)CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H

Historical context and remediation

This reference retains the original CVE publication date. A recent record update does not mean a new attack occurred.

No separately sourced impact summary is available on this page yet. Consult the description, version data and dated exploitation evidence.

No explicit remediation statement is available on this page yet. Consult the original record and vendor references before choosing a fix.

Version statuses below come from the CNA. An “unaffected” version is not necessarily a currently supported release or proof of a patch date. EPSS is a dated risk estimate, not a count of historical attacks.

Read the original CVE record.

Affected products

VendorProductVersions
LinuxLinux
  • Default status: unaffected
  • 31f7efcdca4d1caaa3a0babc33377e27e6f9b593 up to but excluding dce8f7f03a47b1744dccf506268f9229b67fab47 (affected)
  • 31f7efcdca4d1caaa3a0babc33377e27e6f9b593 up to but excluding 6467c4cc83b94850bfea614e9f98276edf9a7c3f (affected)
  • 31f7efcdca4d1caaa3a0babc33377e27e6f9b593 up to but excluding 3c44cbcec5eb370713bbd2c315ed7c34d8ccec2b (affected)
LinuxLinux
  • Default status: affected
  • 6.16 (affected)
  • 0 up to but excluding 6.16 (unaffected)
  • 6.18.59 up to and including 6.18.* (unaffected)
  • 7.2.13 up to and including 7.2.* (unaffected)
  • 7.3 up to and including * (unaffected)

Timeline

  1. 28 Oct 2026 Published

References