CVE-2026-80618drm/amdkfd: Avoid double-unpin of DOORBELL/MMIO BOs on free
- —Not scoredno CVSS score yet
- 0.21%Exploitation in 30 daysEPSS · top 88% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
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)
Timeline
ID reserved
By Linux
- 2 days later
· 2 days later
Published
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.
- EPSS (exploitation in 30 days)
- 0.21% · top 88% of all CVEs (18 Nov 2026)
The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.
Affected products
- affected d25e35bc26c3ca8cd728101545cfb3e86a5d7431 – < 461ae406ae12107ebb321cabe561434c27aaea58
- affected d25e35bc26c3ca8cd728101545cfb3e86a5d7431 – < 283e77af49fda96aaa57709fc5408b55ffec075e
- affected d25e35bc26c3ca8cd728101545cfb3e86a5d7431 – < c055a2088b719e9a4b580685e0ca97f9554a41a8
- affected d25e35bc26c3ca8cd728101545cfb3e86a5d7431 – < 0e27d92f69b8e4c750a4b181cc05a86b9338c4f5
- affected d25e35bc26c3ca8cd728101545cfb3e86a5d7431 – < 1d12ae8b079e173107abec0e5817332954c8e95f
- affected d25e35bc26c3ca8cd728101545cfb3e86a5d7431 – < 3f0cc1735273a57c5116710cf0202e12152f59cc
- affected 5.17
- unaffected < 5.17
- unaffected 6.1.178 – ≤ 6.1.*
- unaffected 6.6.145 – ≤ 6.6.*
- unaffected 6.12.97 – ≤ 6.12.*
- unaffected 6.18.40 – ≤ 6.18.*
- unaffected 7.1.5 – ≤ 7.1.*
- unaffected 7.2 – ≤ *
References
References6
- https://git.kernel.org/stable/c/461ae406ae12107ebb321cabe561434c27aaea58 (opens in a new tab)
- https://git.kernel.org/stable/c/283e77af49fda96aaa57709fc5408b55ffec075e (opens in a new tab)
- https://git.kernel.org/stable/c/c055a2088b719e9a4b580685e0ca97f9554a41a8 (opens in a new tab)
- https://git.kernel.org/stable/c/0e27d92f69b8e4c750a4b181cc05a86b9338c4f5 (opens in a new tab)
- https://git.kernel.org/stable/c/1d12ae8b079e173107abec0e5817332954c8e95f (opens in a new tab)
- https://git.kernel.org/stable/c/3f0cc1735273a57c5116710cf0202e12152f59cc (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2026-67494 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2026-80618)Record last updated .