Vulnerability-Lookup

CVE-2026-80919 (GCVE-0-2026-80919)

Vulnerability from cvelistv5 – Published: 2026-09-09 16:13 – Updated: 2026-09-09 16:13

Title

drm/amdgpu: fix recursive ww_mutex acquire in amdgpu_devcoredump_format

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 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)

Severity

No CVSS data available.

Assigner

Linux mitre root

References

2 references

URL	Tags
https://git.kernel.org/stable/c/4e9b4dee0777ec9c8…
https://git.kernel.org/stable/c/7152b248dc3c8d5fa…

Impacted products

2 products

Vendor	Product	Version	CPE status
Linux	Linux	Affected: 7b15fc2d1f1a00fb99f0146e404ff2600999ec74 , < 4e9b4dee0777ec9c835a4746e2d30382dd9d1044 (git) Affected: 7b15fc2d1f1a00fb99f0146e404ff2600999ec74 , < 7152b248dc3c8d5fa8629e99ed5655dd41b51562 (git)	guessed
Linux	Linux	Affected: 7.1 Unaffected: 0 , < 7.1 (semver) Unaffected: 7.1.11 , ≤ 7.1.* (semver) Unaffected: 7.2 , ≤ * (original_commit_for_fix)	guessed

Show details on NVD website

JSON

To clipboard

{
  "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\u0027s 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",
  "vulnerability-lookup:meta": {
    "nvd": "{\"cve\":{\"id\":\"CVE-2026-80919\",\"sourceIdentifier\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"published\":\"2026-09-09T17:17:47.003\",\"lastModified\":\"2026-09-09T17:17:47.003\",\"vulnStatus\":\"Received\",\"cveTags\":[],\"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\u0027s 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)\"}],\"affected\":[{\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"affectedData\":[{\"vendor\":\"Linux\",\"product\":\"Linux\",\"defaultStatus\":\"unaffected\",\"programFiles\":[\"drivers/gpu/drm/amd/amdgpu/amdgpu_dev_coredump.c\"],\"repo\":\"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git\",\"versions\":[{\"version\":\"7b15fc2d1f1a00fb99f0146e404ff2600999ec74\",\"lessThan\":\"4e9b4dee0777ec9c835a4746e2d30382dd9d1044\",\"versionType\":\"git\",\"status\":\"affected\"},{\"version\":\"7b15fc2d1f1a00fb99f0146e404ff2600999ec74\",\"lessThan\":\"7152b248dc3c8d5fa8629e99ed5655dd41b51562\",\"versionType\":\"git\",\"status\":\"affected\"}]},{\"vendor\":\"Linux\",\"product\":\"Linux\",\"defaultStatus\":\"affected\",\"programFiles\":[\"drivers/gpu/drm/amd/amdgpu/amdgpu_dev_coredump.c\"],\"repo\":\"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git\",\"versions\":[{\"version\":\"7.1\",\"status\":\"affected\"},{\"version\":\"0\",\"lessThan\":\"7.1\",\"versionType\":\"semver\",\"status\":\"unaffected\"},{\"version\":\"7.1.11\",\"lessThanOrEqual\":\"7.1.*\",\"versionType\":\"semver\",\"status\":\"unaffected\"},{\"version\":\"7.2\",\"lessThanOrEqual\":\"*\",\"versionType\":\"original_commit_for_fix\",\"status\":\"unaffected\"}]}]}],\"metrics\":{},\"references\":[{\"url\":\"https://git.kernel.org/stable/c/4e9b4dee0777ec9c835a4746e2d30382dd9d1044\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"},{\"url\":\"https://git.kernel.org/stable/c/7152b248dc3c8d5fa8629e99ed5655dd41b51562\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"}]}}"
  }
}

FKIE_CVE-2026-80919

Vulnerability from fkie_nvd - Published: 2026-09-09 17:17 - Updated: 2026-09-09 17:17

Severity

Summary

References

	URL	Tags
	416baaa9-dc9f-4396-8d5f-8c081fb06d67	https://git.kernel.org/stable/c/4e9b4dee0777ec9c835a4746e2d30382dd9d1044
	416baaa9-dc9f-4396-8d5f-8c081fb06d67	https://git.kernel.org/stable/c/7152b248dc3c8d5fa8629e99ed5655dd41b51562

Impacted products

	Vendor	Product	Version

JSON

To clipboard

{
  "affected": [
    {
      "affectedData": [
        {
          "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"
            }
          ]
        }
      ],
      "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
    }
  ],
  "cveTags": [],
  "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\u0027s 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)"
    }
  ],
  "id": "CVE-2026-80919",
  "lastModified": "2026-09-09T17:17:47.003",
  "metrics": {},
  "published": "2026-09-09T17:17:47.003",
  "references": [
    {
      "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
      "url": "https://git.kernel.org/stable/c/4e9b4dee0777ec9c835a4746e2d30382dd9d1044"
    },
    {
      "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
      "url": "https://git.kernel.org/stable/c/7152b248dc3c8d5fa8629e99ed5655dd41b51562"
    }
  ],
  "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
  "vulnStatus": "Received"
}

GHSA-97PV-PQPM-W4FG

Vulnerability from github – Published: 2026-09-09 18:32 – Updated: 2026-09-09 18:32

Details

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)

Show details on source website

JSON

To clipboard

{
  "affected": [],
  "aliases": [
    "CVE-2026-80919"
  ],
  "database_specific": {
    "cwe_ids": [],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2026-09-09T17:17:47Z",
    "severity": null
  },
  "details": "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\u0027s 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)",
  "id": "GHSA-97pv-pqpm-w4fg",
  "modified": "2026-09-09T18:32:04Z",
  "published": "2026-09-09T18:32:04Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-80919"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/4e9b4dee0777ec9c835a4746e2d30382dd9d1044"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/7152b248dc3c8d5fa8629e99ed5655dd41b51562"
    }
  ],
  "schema_version": "1.4.0",
  "severity": []
}

Sightings

Author	Source	Type	Date	Other

Nomenclature

Seen: The vulnerability was mentioned, discussed, or observed by the user.
Confirmed: The vulnerability has been validated from an analyst's perspective.
Published Proof of Concept: A public proof of concept is available for this vulnerability.
Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
Not confirmed: The user expressed doubt about the validity of the vulnerability.
Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.

Detection rules are retrieved from Rulezet.

The MITRE ATT&CK techniques below are AI-generated suggestions, inferred from the description of the vulnerability by the CIRCL/vulnerability-attack-technique-classification-roberta-base model, served locally by ML-Gateway. They have not been verified by an analyst and are provided for guidance only.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.

Action not permitted

CVE-2026-80919 (GCVE-0-2026-80919)

FKIE_CVE-2026-80919

GHSA-97PV-PQPM-W4FG

Tags

Sightings

Nomenclature