CVE-2026-80618

drm/amdkfd: Avoid double-unpin of DOORBELL/MMIO BOs on free

Published Aug 28, 2026 CVSS 3.1 · 5.5 Medium EPSS < 1% KEV · Not listed
Description
In the Linux kernel, the following vulnerability has been resolved:

drm/amdkfd: Avoid double-unpin of DOORBELL/MMIO BOs on free

amdgpu_amdkfd_gpuvm_free_memory_of_gpu() unpinned DOORBELL and MMIO
remap BOs (which are pinned at allocation time) before checking whether
the BO is still mapped to the GPU. When the BO is still mapped, the
function returns -EBUSY and leaves the BO alive, but it has already
been unpinned. The BO is then unpinned again when it is finally freed
during process teardown, triggering a ttm_bo_unpin() underflow warning:

WARNING: CPU: 18 PID: 15066 at ttm/ttm_bo.c:650 amdttm_bo_unpin+0x6d/0x80 [amdttm]
Workqueue: kfd_process_wq kfd_process_wq_release [amdgpu]
RIP: 0010:amdttm_bo_unpin+0x6d/0x80 [amdttm]
Call Trace:
amdgpu_bo_unpin+0x1a/0x90 [amdgpu]
amdgpu_amdkfd_gpuvm_unpin_bo+0x31/0xb0 [amdgpu]
amdgpu_amdkfd_gpuvm_free_memory_of_gpu+0x3bf/0x460 [amdgpu]
kfd_process_free_outstanding_kfd_bos+0xd4/0x170 [amdgpu]
kfd_process_wq_release+0x109/0x1b0 [amdgpu]
process_one_work+0x1e2/0x3b0
worker_thread+0x50/0x3a0
kthread+0xdd/0x100
ret_from_fork+0x29/0x50

Move the unpin after the mapped_to_gpu_memory check so it only happens
once we are committed to freeing the BO.

(cherry picked from commit 927c5b2defb9b09856444d94bebfd056a002bd75)

Analysis

AI-generated

Technical impact

Based on the description, it is inferred that the attack vector involves local kernel manipulation via GPU buffer object allocation and deallocation. A defect in the AMDGPU amdkfd GPU memory manager of the Linux kernel causes a buffer object (BO) to be unpinned twice during process teardown. The code removes the pin on a doorbell or MMIO BO before it confirms that the BO is still mapped to the GPU. When the BO remains mapped, the function returns an error but the BO has already been unpinned; a second unpin during final deallocation then triggers an underflow warning in ttm_bo_unpin(). This double‑unpin can corrupt the reference counter of the BO and may lead to a kernel panic or at least repeated warning messages, effectively providing a denial‑of‑service weakness for code that can manipulate AMDKFD GPU memory. The fix reorders the unpin operation to prevent the double‑unpin but does not provide an alternative mitigation path beyond updating the kernel.

Affected Systems

Based on the description, it is inferred that the attack vector requires local access to the GPU subsystem. All users of the Linux kernel that include the vulnerable AMDKFD code path, specifically those running the AMDGPU driver on AMD GPUs. The defect exists in kernel versions that predate commit 927c5b2defb9b09856444d94bebfd056a002bd75. Vendor information is limited to the Linux kernel itself with no version lattice supplied.

Risk and Exploitability

Based on the description, it is inferred that the attack vector is local to user‑space processes that allocate GPU buffers. The vulnerability requires entry into kernel space, so it is effectively a local escalation or a bug that can be triggered by any process that allocates and later frees GPU buffer objects. No public exploit has been documented and there is no KEV listing. The EPSS score is <1%, indicating a very low exploitation probability. Nonetheless, the fault can cause kernel instability and potentially a crash under normal GPU workloads, presenting a high risk of denial of service. The CVSS score of 5.5 indicates a medium severity vulnerability. The fix reorders the unpin operation to prevent the double‑unpin but does not provide an alternative mitigation path beyond updating the kernel.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Apply a kernel update that includes commit 927c5b2defb9b09856444d94bebfd056a002bd75 or any later release that contains the AMDKFD fix, addressing the double‑unpin flaw identified as CWE‑832.
  • Update the AMDGPU driver package to the most recent distribution signed release or rebuild from source to ensure the driver is aligned with the patched kernel, mitigating the underlying resource‑management issues related to the double‑unpin flaw (CWE‑832).
  • If an update cannot be applied immediately, limit GPU access for untrusted or privileged user processes and monitor for kernel panic logs to detect premature faults, which may arise from double‑unpin causing resource mismanagement or positional errors (CWE‑832).

Generated by OpenCVE AI on August 31, 2026 at 16:46 UTC.

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
Ubuntu USN Ubuntu USN USN-8887-1 Linux kernel vulnerabilities
Ubuntu USN Ubuntu USN USN-8888-1 Linux kernel (Azure) vulnerabilities
Ubuntu USN Ubuntu USN USN-8889-1 Linux kernel (OEM) vulnerabilities
Ubuntu USN Ubuntu USN USN-8887-2 Linux kernel (AWS) vulnerabilities
Ubuntu USN Ubuntu USN USN-8888-2 Linux kernel (Azure) vulnerabilities
Ubuntu USN Ubuntu USN USN-8887-3 Linux kernel vulnerabilities
Ubuntu USN Ubuntu USN USN-8917-1 Linux kernel vulnerabilities
Ubuntu USN Ubuntu USN USN-8918-1 Linux kernel (Azure) vulnerabilities
Ubuntu USN Ubuntu USN USN-9003-1 Linux kernel (NVIDIA) vulnerabilities
Ubuntu USN Ubuntu USN USN-9024-1 Linux kernel vulnerabilities
Ubuntu USN Ubuntu USN USN-9025-1 Linux kernel vulnerabilities
Ubuntu USN Ubuntu USN USN-9026-1 Linux kernel (Azure) vulnerabilities
Ubuntu USN Ubuntu USN USN-9040-1 Linux kernel (Low Latency NVIDIA) vulnerabilities
Ubuntu USN Ubuntu USN USN-9043-1 Linux kernel (NVIDIA) vulnerabilities
Ubuntu USN Ubuntu USN USN-9066-1 Linux kernel (HWE) vulnerabilities
Ubuntu USN Ubuntu USN USN-9091-1 Linux kernel (NVIDIA Tegra) vulnerabilities
History
Type Values Removed Values Added
Weaknesses CWE-399
CWE-416
Type Values Removed Values Added
Weaknesses CWE-832
References
Metrics threat_severity

None

cvssV3_1

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

threat_severity

Moderate

Type Values Removed Values Added
Weaknesses CWE-399
CWE-416
Type Values Removed Values Added
Description In the Linux kernel, the following vulnerability has been resolved: drm/amdkfd: Avoid double-unpin of DOORBELL/MMIO BOs on free amdgpu_amdkfd_gpuvm_free_memory_of_gpu() unpinned DOORBELL and MMIO remap BOs (which are pinned at allocation time) before checking whether the BO is still mapped to the GPU. When the BO is still mapped, the function returns -EBUSY and leaves the BO alive, but it has already been unpinned. The BO is then unpinned again when it is finally freed during process teardown, triggering a ttm_bo_unpin() underflow warning: WARNING: CPU: 18 PID: 15066 at ttm/ttm_bo.c:650 amdttm_bo_unpin+0x6d/0x80 [amdttm] Workqueue: kfd_process_wq kfd_process_wq_release [amdgpu] RIP: 0010:amdttm_bo_unpin+0x6d/0x80 [amdttm] Call Trace: amdgpu_bo_unpin+0x1a/0x90 [amdgpu] amdgpu_amdkfd_gpuvm_unpin_bo+0x31/0xb0 [amdgpu] amdgpu_amdkfd_gpuvm_free_memory_of_gpu+0x3bf/0x460 [amdgpu] kfd_process_free_outstanding_kfd_bos+0xd4/0x170 [amdgpu] kfd_process_wq_release+0x109/0x1b0 [amdgpu] process_one_work+0x1e2/0x3b0 worker_thread+0x50/0x3a0 kthread+0xdd/0x100 ret_from_fork+0x29/0x50 Move the unpin after the mapped_to_gpu_memory check so it only happens once we are committed to freeing the BO. (cherry picked from commit 927c5b2defb9b09856444d94bebfd056a002bd75)
Title drm/amdkfd: Avoid double-unpin of DOORBELL/MMIO BOs on free
First Time appeared Linux
Linux linux Kernel
CPEs cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
Vendors & Products Linux
Linux linux Kernel
References
Weaknesses
  • CWE-832

    Unlock of a Resource that is not Locked

Sources

Status
PUBLISHED
Assigner
Linux
Published
Updated
Aug 28, 2026, 6:48 AM
Reserved
Aug 26, 2026, 2:34 PM
Status
Received
Published
Aug 28, 2026, 8:16 AM
Modified
Aug 28, 2026, 8:16 AM
Severity
Moderate
Public date
Aug 28, 2026, 12:00 AM