{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-80618 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-80618 is an use after free vulnerability in Linux, published on 28 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-80618 and fix it if it is affected.\n\nWhat it is: CVE-2026-80618 is an use after free vulnerability in Linux, published on 28 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-80618 in the wild and no public exploit code.\n\nAffected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-80618/ (Markdown: https://insights.sbomify.com/CVE-2026-80618/index.md)","id":"CVE-2026-80618","markdown":"https://insights.sbomify.com/CVE-2026-80618/index.md","name":"CVE-2026-80618","record":{"aliases":["BELL-CVE-2026-80618","DEBIAN-CVE-2026-80618","GHSA-82jr-fm8v-cx8j","UBUNTU-CVE-2026-80618"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel driver","requires_auth":"low_privilege","summary":"A local attacker can trigger a double-unpin error in the AMD KFD driver, causing a kernel warning and potential system instability.","user_interaction":"not_required","vuln_class":"use_after_free"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"In the Linux kernel, the following vulnerability has been resolved:\n\ndrm/amdkfd: Avoid double-unpin of DOORBELL/MMIO BOs on free\n\namdgpu_amdkfd_gpuvm_free_memory_of_gpu() unpinned DOORBELL and MMIO\nremap BOs (which are pinned at allocation time) before checking whether\nthe BO is still mapped to the GPU. When the BO is still mapped, the\nfunction returns -EBUSY and leaves the BO alive, but it has already\nbeen unpinned. The BO is then unpinned again when it is finally freed\nduring process teardown, triggering a ttm_bo_unpin() underflow warning:\n\n  WARNING: CPU: 18 PID: 15066 at ttm/ttm_bo.c:650 amdttm_bo_unpin+0x6d/0x80 [amdttm]\n  Workqueue: kfd_process_wq kfd_process_wq_release [amdgpu]\n  RIP: 0010:amdttm_bo_unpin+0x6d/0x80 [amdttm]\n  Call Trace:\n   amdgpu_bo_unpin+0x1a/0x90 [amdgpu]\n   amdgpu_amdkfd_gpuvm_unpin_bo+0x31/0xb0 [amdgpu]\n   amdgpu_amdkfd_gpuvm_free_memory_of_gpu+0x3bf/0x460 [amdgpu]\n   kfd_process_free_outstanding_kfd_bos+0xd4/0x170 [amdgpu]\n   kfd_process_wq_release+0x109/0x1b0 [amdgpu]\n   process_one_work+0x1e2/0x3b0\n   worker_thread+0x50/0x3a0\n   kthread+0xdd/0x100\n   ret_from_fork+0x29/0x50\n\nMove the unpin after the mapped_to_gpu_memory check so it only happens\nonce we are committed to freeing the BO.\n\n(cherry picked from commit 927c5b2defb9b09856444d94bebfd056a002bd75)","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"drm/amdkfd: Avoid double-unpin of DOORBELL/MMIO BOs on free","id":"CVE-2026-80618","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"use_after_free","year":"2026"},"n_packages":0,"n_references":6,"next":{"headline":"apparmor: fix potential UAF in aa_replace_profiles","id":"CVE-2026-80619"},"packages":[],"prev":{"headline":"net: airoha: fix foe_check_time allocation size","id":"CVE-2026-80617"},"products":["Linux"],"published":"2026-08-28","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-08-28","vendors":["Linux"]},"summary":"A local attacker can trigger a double-unpin error in the AMD KFD driver, causing a kernel warning and potential system instability.","url":"https://insights.sbomify.com/CVE-2026-80618/"}