CVE-2026-80618

CVE CVE-2026-80618EUVD EUVD-2026-67494Published 2026-08-28T06:48:38.000Z

What the advisory describes

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)

Source: EUVD (ENISA), in the words of the advisory.

Products the advisory names

These come from the advisory itself, not from any check we performed.

Linux — Linux patch: 6.18.40; d25e35bc26c3ca8cd728101545cfb3e86a5d7431 <c055a2088b719e9a4b580685e0ca97f9554a41a8; patch: 7.1.5; patch: 6.12.97; 5.17; d25e35bc26c3ca8cd728101545cfb3e86a5d7431 <0e27d92f69b8e4c750a4b181cc05a86b9338c4f5; d25e35bc26c3ca8cd728101545cfb3e86a5d7431 <1d12ae8b079e173107abec0e5817332954c8e95f; patch: 6.6.145; d25e35bc26c3ca8cd728101545cfb3e86a5d7431 <3f0cc1735273a57c5116710cf0202e12152f59cc; patch: 0; patch: 6.1.178; patch: 7.2; d25e35bc26c3ca8cd728101545cfb3e86a5d7431 <461ae406ae12107ebb321cabe561434c27aaea58; d25e35bc26c3ca8cd728101545cfb3e86a5d7431 <283e77af49fda96aaa57709fc5408b55ffec075e

The versions shown are the advisory's own. Patchlage compares no version numbers and derives no judgement from them — which version is installed is something a person has to look up.

Carried in the product catalogue

An estate covering these products can be recorded in Patchlage. An advisory about them appears in the next morning's situation report.

Linux — Linux

Does this concern one of your customers?

This page cannot answer that — it does not know your estate. Whoever has recorded their environments gets the answer the morning after publication, together with a paragraph they can forward to the customer unedited.

Try it for 28 days

Patchlage reports hits and suspected hits. About everything else this system says nothing — neither this page nor the situation report ever claims that an estate is safe.