CVE-2026-99148

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

Published Oct 28, 2026 CVSS 3.1 · 7 High EPSS < 1% KEV · Not listed
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)

Analysis

AI-generated

Technical impact

The AMDGPU driver in the Linux kernel accidentally detaches a buffer object's eviction fence when a handle is closed, even while other handles and memory mappings remain open. This premature removal allows the buffer to be evicted from GPU memory while user queues still reference it, which can lead to crashes, data corruption, or a loss of service for GPU workloads. This improper resource management flaw (CWE-825) results in a denial of service condition.

Affected Systems

Any Linux kernel that ships with the AMDGPU driver is potentially affected. The issue was observed on an AMD Navi31 platform using an SDMA user queue: a buffer object opened twice in the same file lost its eviction fence when the second handle was closed while the first handle and mapping continued to be used.

Risk and Exploitability

The flaw requires manipulating AMDGPU buffer handles, so it is a local kernel issue that would normally be exercised by privileged code or an attacker who can load a custom kernel module or driver. Based on the description, it is inferred that an attacker would need to perform a local attack with elevated privileges to trigger this defect. The likely attack vector is local privilege escalation that allows loading of a custom driver or kernel module. The CVSS score is 7, and the EPSS score is less than 1%. The vulnerability is not listed in CISA KEV, indicating no publicly known widespread exploitation. Attackers with local privilege or the ability to run privileged code can potentially trigger the defect, making it a notable risk for affected systems.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Apply a kernel that includes the commit 8387982f03d4026b7dc11b0b5e3118298eee4d6a, which corrects the eviction fence handling logic.
  • Reboot the system so the updated kernel and driver are active.
  • If your distribution does not provide a patched kernel, manually apply the patch to the kernel source, rebuild the kernel modules, and reboot.

Generated by OpenCVE AI on October 31, 2026 at 13:22 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
Metrics cvssV3_1

{'score': 7.8, 'vector': 'CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H'}

cvssV3_1

{'score': 7, 'vector': 'CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H'}

Type Values Removed Values Added
Weaknesses CWE-400
CWE-772
Type Values Removed Values Added
Weaknesses CWE-825
References
Metrics threat_severity

None

cvssV3_1

{'score': 7.8, 'vector': 'CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H'}

threat_severity

Important

Type Values Removed Values Added
First Time appeared Linux linux
Weaknesses CWE-400
CWE-772
Vendors & Products Linux linux
Type Values Removed Values Added
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)
Title drm/amdgpu: keep the eviction fence until the last handle is closed
First Time appeared Linux
Linux linux Kernel
CPEs cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
Vendors & Products Linux
Linux linux Kernel
References
Weaknesses
  • CWE-825

    Expired Pointer Dereference

Sources

Status
PUBLISHED
Assigner
Linux
Published
Updated
Oct 31, 2026, 12:43 PM
Reserved
Sep 25, 2026, 10:25 AM
Status
Received
Published
Oct 28, 2026, 11:17 AM
Modified
Oct 31, 2026, 1:17 PM
Severity
Important
Public date
Oct 28, 2026, 10:35 AM