{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-80919 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-80919 is a denial of service vulnerability in Linux, published on 9 Sep 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-80919 and fix it if it is affected.\n\nWhat it is: CVE-2026-80919 is a denial of service vulnerability in Linux, published on 9 Sep 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-80919 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-80919/ (Markdown: https://insights.sbomify.com/CVE-2026-80919/index.md)","id":"CVE-2026-80919","markdown":"https://insights.sbomify.com/CVE-2026-80919/index.md","name":"CVE-2026-80919","record":{"aliases":["DEBIAN-CVE-2026-80919","GHSA-97pv-pqpm-w4fg","UBUNTU-CVE-2026-80919"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":true,"product_category":"Linux kernel driver","requires_auth":"none","summary":"A recursive locking bug in the amdgpu driver can cause a kernel deadlock and log flooding when dumping hung jobs, leading to denial of service.","user_interaction":"not_required","vuln_class":"denial_of_service"},"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/amdgpu: fix recursive ww_mutex acquire in amdgpu_devcoredump_format\n\nWhen dumping IB contents from a hung job, amdgpu_devcoredump_format()\nacquired the VM root PD's reservation via amdgpu_vm_lock_by_pasid() and\nthen, for each IB, called amdgpu_bo_reserve() on the BO backing the IB.\nBoth reservations are reservation_ww_class_mutex objects and neither\nused a ww_acquire_ctx, which trips lockdep:\n\n  WARNING: possible recursive locking detected\n  --------------------------------------------\n  kworker/u128:0 is trying to acquire lock:\n  ffff88838b16e1f0 (reservation_ww_class_mutex){+.+.}-{4:4},\n    at: amdgpu_devcoredump_format+0x1594/0x23f0 [amdgpu]\n\n  but task is already holding lock:\n  ffff8882f82681f0 (reservation_ww_class_mutex){+.+.}-{4:4},\n    at: amdgpu_devcoredump_format+0x1594/0x23f0 [amdgpu]\n\n   Possible unsafe locking scenario:\n         CPU0\n         ----\n    lock(reservation_ww_class_mutex);\n    lock(reservation_ww_class_mutex);\n\n   *** DEADLOCK ***\n   May be due to missing lock nesting notation\n\n  Workqueue: events_unbound amdgpu_devcoredump_deferred_work [amdgpu]\n  Call Trace:\n   __ww_mutex_lock.constprop.0\n   ww_mutex_lock\n   amdgpu_bo_reserve\n   amdgpu_devcoredump_format+0x1594 [amdgpu]\n   amdgpu_devcoredump_deferred_work+0xea [amdgpu]\n\nThe two reservations are on different BOs in the captured trace, so the\nsplat is a lockdep-correctness warning, not an observed deadlock. It\nbecomes a real self-deadlock whenever the IB BO shares its dma_resv with\nthe root PD (the always-valid case, see amdgpu_vm_is_bo_always_valid()):\namdgpu_bo_reserve(abo) re-acquires the same ww_mutex without a ticket\nand blocks forever. With amdgpu.gpu_recovery=0 the timeout handler\nrefires every ~2 s and each invocation produces this splat, drowning the\nkernel ring buffer.\n\nNow that amdgpu_vm_lock_by_pasid() takes a drm_exec context, move the IB\ndumping into a separate helper that locks the root PD and every IB BO\ntogether in a single drm_exec ticket. DRM_EXEC_IGNORE_DUPLICATES handles\nIB BOs that share a dma_resv (e.g. always-valid BOs, or two IBs backed\nby the same BO). Every lock is now a top-level acquire under one\nww_acquire_ctx, so the recursive ww_mutex condition is gone, and the\nper-IB amdgpu_bo_reserve()/amdgpu_bo_unref() dance -- including a BO\nrefcount leak on the amdgpu_bo_reserve() failure path -- is removed.\n\n(cherry picked from commit d6bf4242731219ee08ce54c365631e395486651e)","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/amdgpu: fix recursive ww_mutex acquire in amdgpu_devcoredump_format","id":"CVE-2026-80919","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"denial_of_service","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"io_uring: defer eventfd signaling when queued from a wakeup handler","id":"CVE-2026-80920"},"packages":[],"prev":{"headline":"HID: core: fix number/pointer type confusion on long items","id":"CVE-2026-80918"},"products":["Linux"],"published":"2026-09-09","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-09-09","vendors":["Linux"]},"summary":"A recursive locking bug in the amdgpu driver can cause a kernel deadlock and log flooding when dumping hung jobs, leading to denial of service.","url":"https://insights.sbomify.com/CVE-2026-80919/"}