{"api_version":"1","generated_at":"2026-09-10T22:38:12+00:00","cve":"CVE-2026-80919","urls":{"html":"https://cve.report/CVE-2026-80919","api":"https://cve.report/api/cve/CVE-2026-80919.json","docs":"https://cve.report/api","cve_org":"https://www.cve.org/CVERecord?id=CVE-2026-80919","nvd":"https://nvd.nist.gov/vuln/detail/CVE-2026-80919"},"summary":{"title":"drm/amdgpu: fix recursive ww_mutex acquire in amdgpu_devcoredump_format","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)","state":"PUBLISHED","assigner":"Linux","published_at":"2026-09-09 17:17:47","updated_at":"2026-09-09 17:17:47"},"problem_types":[],"metrics":[],"references":[{"url":"https://git.kernel.org/stable/c/7152b248dc3c8d5fa8629e99ed5655dd41b51562","name":"https://git.kernel.org/stable/c/7152b248dc3c8d5fa8629e99ed5655dd41b51562","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/4e9b4dee0777ec9c835a4746e2d30382dd9d1044","name":"https://git.kernel.org/stable/c/4e9b4dee0777ec9c835a4746e2d30382dd9d1044","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-80919","name":"CVE Program record","refsource":"CVE.ORG","tags":["canonical"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-80919","name":"NVD vulnerability detail","refsource":"NVD","tags":["canonical","analysis"]}],"affected":[{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 7b15fc2d1f1a00fb99f0146e404ff2600999ec74 4e9b4dee0777ec9c835a4746e2d30382dd9d1044 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 7b15fc2d1f1a00fb99f0146e404ff2600999ec74 7152b248dc3c8d5fa8629e99ed5655dd41b51562 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 7.1","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.1 semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.1.11 7.1.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.2 * original_commit_for_fix","platforms":[]}],"timeline":[],"solutions":[],"workarounds":[],"exploits":[],"credits":[],"nvd_cpes":[],"vendor_comments":[],"enrichments":{"kev":null,"epss":null,"legacy_qids":[]},"source_records":{"cve_program":{"containers":{"cna":{"affected":[{"defaultStatus":"unaffected","product":"Linux","programFiles":["drivers/gpu/drm/amd/amdgpu/amdgpu_dev_coredump.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"lessThan":"4e9b4dee0777ec9c835a4746e2d30382dd9d1044","status":"affected","version":"7b15fc2d1f1a00fb99f0146e404ff2600999ec74","versionType":"git"},{"lessThan":"7152b248dc3c8d5fa8629e99ed5655dd41b51562","status":"affected","version":"7b15fc2d1f1a00fb99f0146e404ff2600999ec74","versionType":"git"}]},{"defaultStatus":"affected","product":"Linux","programFiles":["drivers/gpu/drm/amd/amdgpu/amdgpu_dev_coredump.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"status":"affected","version":"7.1"},{"lessThan":"7.1","status":"unaffected","version":"0","versionType":"semver"},{"lessThanOrEqual":"7.1.*","status":"unaffected","version":"7.1.11","versionType":"semver"},{"lessThanOrEqual":"*","status":"unaffected","version":"7.2","versionType":"original_commit_for_fix"}]}],"cpeApplicability":[{"nodes":[{"cpeMatch":[{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.1.11","versionStartIncluding":"7.1","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.2","versionStartIncluding":"7.1","vulnerable":true}],"negate":false,"operator":"OR"}]}],"descriptions":[{"lang":"en","value":"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)"}],"providerMetadata":{"dateUpdated":"2026-09-09T16:13:16.415Z","orgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","shortName":"Linux"},"references":[{"url":"https://git.kernel.org/stable/c/4e9b4dee0777ec9c835a4746e2d30382dd9d1044"},{"url":"https://git.kernel.org/stable/c/7152b248dc3c8d5fa8629e99ed5655dd41b51562"}],"title":"drm/amdgpu: fix recursive ww_mutex acquire in amdgpu_devcoredump_format","x_generator":{"engine":"bippy-1.2.0"}}},"cveMetadata":{"assignerOrgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","assignerShortName":"Linux","cveId":"CVE-2026-80919","datePublished":"2026-09-09T16:13:16.415Z","dateReserved":"2026-08-26T14:34:25.801Z","dateUpdated":"2026-09-09T16:13:16.415Z","state":"PUBLISHED"},"dataType":"CVE_RECORD","dataVersion":"5.2"},"nvd":{"publishedDate":"2026-09-09 17:17:47","lastModifiedDate":"2026-09-09 17:17:47","problem_types":[],"metrics":[],"configurations":[]},"legacy_mitre":{"record":{"CveYear":"2026","CveId":"80919","Ordinal":"1","Title":"drm/amdgpu: fix recursive ww_mutex acquire in amdgpu_devcoredump","CVE":"CVE-2026-80919","Year":"2026"},"notes":[{"CveYear":"2026","CveId":"80919","Ordinal":"1","NoteData":"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)","Type":"Description","Title":"drm/amdgpu: fix recursive ww_mutex acquire in amdgpu_devcoredump"}]}}}