---
id: CVE-2026-80919
title: |-
  In the Linux kernel, the following vulnerability has been resolved:

  drm/amdgpu: fix recursive ww_mutex acquire in amdgpu_devcoredump_format

  When dumping IB contents from a hung job, amdgpu_devcoredump_format()
  acquired the VM root PD's…
summary: |-
  In the Linux kernel, the following vulnerability has been resolved:

  drm/amdgpu: fix recursive ww_mutex acquire in amdgpu_devcoredump_format

  When dumping IB contents from a hung job, amdgpu_devcoredump_format()
  acquired the VM root PD's…
severity: medium
vendor: Linux
product: Linux
affected:
  - >-
    Linux >= 7b15fc2d1f1a00fb99f0146e404ff2600999ec74 <
    4e9b4dee0777ec9c835a4746e2d30382dd9d1044
  - >-
    Linux >= 7b15fc2d1f1a00fb99f0146e404ff2600999ec74 <
    7152b248dc3c8d5fa8629e99ed5655dd41b51562
  - Linux 7.1
published: '2026-09-09'
updated: '2026-09-09'
sourceUpdated: '2026-09-09T17:17:47.003'
source: NVD
sourceUrl: 'https://nvd.nist.gov/vuln/detail/CVE-2026-80919'
references:
  - url: 'https://git.kernel.org/stable/c/4e9b4dee0777ec9c835a4746e2d30382dd9d1044'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/7152b248dc3c8d5fa8629e99ed5655dd41b51562'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: >-
      https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-80919.json
  - url: 'https://access.redhat.com/security/cve/CVE-2026-80919'
  - url: 'https://bugzilla.redhat.com/show_bug.cgi?id=2531054'
  - url: 'https://www.cve.org/CVERecord?id=CVE-2026-80919'
  - url: 'https://nvd.nist.gov/vuln/detail/CVE-2026-80919'
  - url: >-
      https://git.kernel.org/pub/scm/linux/security/vulns.git/plain/cve/published/2026/CVE-2026-80919.mbox
tags:
  - nvd
  - cve.org
  - csaf
  - vex
  - red-hat
ingestedAt: '2026-09-09T17:16:03.091Z'
epss: 0.00148
epssPercentile: 0.04367
cvss: 5.5
cvssVector: 'CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H'
cvssSource: vendor
cwe:
  - CWE-833
---

## Overview

In the Linux kernel, the following vulnerability has been resolved:

drm/amdgpu: fix recursive ww_mutex acquire in amdgpu_devcoredump_format

When dumping IB contents from a hung job, amdgpu_devcoredump_format()
acquired the VM root PD's reservation via amdgpu_vm_lock_by_pasid() and
then, for each IB, called amdgpu_bo_reserve() on the BO backing the IB.
Both reservations are reservation_ww_class_mutex objects and neither
used a ww_acquire_ctx, which trips lockdep:

  WARNING: possible recursive locking detected
  --------------------------------------------
  kworker/u128:0 is trying to acquire lock:
  ffff88838b16e1f0 (reservation_ww_class_mutex){+.+.}-{4:4},
    at: amdgpu_devcoredump_format+0x1594/0x23f0 [amdgpu]

  but task is already holding lock:
  ffff8882f82681f0 (reservation_ww_class_mutex){+.+.}-{4:4},
    at: amdgpu_devcoredump_format+0x1594/0x23f0 [amdgpu]

   Possible unsafe locking scenario:
         CPU0
         ----
    lock(reservation_ww_class_mutex);
    lock(reservation_ww_class_mutex);

   *** DEADLOCK ***
   May be due to missing lock nesting notation

  Workqueue: events_unbound amdgpu_devcoredump_deferred_work [amdgpu]
  Call Trace:
   __ww_mutex_lock.constprop.0
   ww_mutex_lock
   amdgpu_bo_reserve
   amdgpu_devcoredump_format+0x1594 [amdgpu]
   amdgpu_devcoredump_deferred_work+0xea [amdgpu]

The two reservations are on different BOs in the captured trace, so the
splat is a lockdep-correctness warning, not an observed deadlock. It
becomes a real self-deadlock whenever the IB BO shares its dma_resv with
the root PD (the always-valid case, see amdgpu_vm_is_bo_always_valid()):
amdgpu_bo_reserve(abo) re-acquires the same ww_mutex without a ticket
and blocks forever. With amdgpu.gpu_recovery=0 the timeout handler
refires every ~2 s and each invocation produces this splat, drowning the
kernel ring buffer.

Now that amdgpu_vm_lock_by_pasid() takes a drm_exec context, move the IB
dumping into a separate helper that locks the root PD and every IB BO
together in a single drm_exec ticket. DRM_EXEC_IGNORE_DUPLICATES handles
IB BOs that share a dma_resv (e.g. always-valid BOs, or two IBs backed
by the same BO). Every lock is now a top-level acquire under one
ww_acquire_ctx, so the recursive ww_mutex condition is gone, and the
per-IB amdgpu_bo_reserve()/amdgpu_bo_unref() dance -- including a BO
refcount leak on the amdgpu_bo_reserve() failure path -- is removed.

(cherry picked from commit d6bf4242731219ee08ce54c365631e395486651e)

## Remediation

Refer to the linked advisories for vendor-supplied fixes and affected version ranges.

## Vendor advisories

- **Red Hat VEX** · Moderate · affected: Red Hat Enterprise Linux 6 · no fix planned: Red Hat Enterprise Linux 6 · updated 2026-09-15 · [vex](https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-80919.json)