VDB

CVE-2025-40329

CVE-2025-40329 PUBLISHED

drm/sched: Fix deadlock in drm_sched_entity_kill_jobs_cb

Reported by linux · Published December 9, 2025

In the Linux kernel, the following vulnerability has been resolved: drm/sched: Fix deadlock in drm_sched_entity_kill_jobs_cb The Mesa issue referenced below pointed out a possible deadlock: [ 1231.611031] Possible interrupt unsafe locking scenario: [ 1231.611033] CPU0 CPU1 [ 1231.611034] ---- ---- [ 1231.611035] lock(&xa->xa_lock#17); [ 1231.611038] local_irq_disable(); [ 1231.611039] lock(&fence->lock); [ 1231.611041] lock(&xa->xa_lock#17); [ 1231.611044] <Interrupt> [ 1231.611045] lock(&fence->lock); [ 1231.611047] *** DEADLOCK *** In this example, CPU0 would be any function accessing job->dependencies through the xa_* functions that don't disable interrupts (eg: drm_sched_job_add_dependency(), drm_sched_entity_kill_jobs_cb()). CPU1 is executing drm_sched_entity_kill_jobs_cb() as a fence signalling callback so in an interrupt context. It will deadlock when trying to grab the xa_lock which is already held by CPU0. Replacing all xa_* usage by their xa_*_irq counterparts would fix this issue, but Christian pointed out another issue: dma_fence_signal takes fence.lock and so does dma_fence_add_callback. dma_fence_signal() // locks f1.lock -> drm_sched_entity_kill_jobs_cb() -> foreach dependencies -> dma_fence_add_callback() // locks f2.lock This will deadlock if f1 and f2 share the same spinlock. To fix both issues, the code iterating on dependencies and re-arming them is moved out to drm_sched_entity_kill_jobs_work(). [phasta: commit message nits]

EPSS 0.24% · 15.1th percentile

Fixed versions

Upgrade to a fixed version or later. Language registries are listed first, then Linux distributions, then vendor products.

PackageEcosystemFixed in
perf6.12Amazon Linux1:6.12.58-82.121.amzn2023

Risk scores

EPSS Score
0.24%
15.1th percentile

Affected products

VendorProductVersions
LinuxLinux2fdb8a8f07c2f1353770a324fd19b8114e4329ac, 2fdb8a8f07c2f1353770a324fd19b8114e4329ac, 2fdb8a8f07c2f1353770a324fd19b8114e4329ac
LinuxLinux6.2, 0, 6.6.117
amazon:2023perf6.120
LinuxLinux2fdb8a8f07c2f1353770a324fd19b8114e4329ac, 2fdb8a8f07c2f1353770a324fd19b8114e4329ac, 0
amazon:2023kernel6.12-modules-extra-common0
amazon:2023kernel-livepatch-6.12.58-82.1210
amazon:2023kernel6.12-modules-extra0
amazon:2023kernel6.12-libbpf-static0
amazon:2023kernel6.12-devel0
amazon:2023python3-perf6.120
amazon:2023kernel6.12-headers0
amazon:2023kernel6.12-libbpf-devel0
amazon:2023kernel6.12-tools-devel0
linuxlinux_kernel6.2, 6.2, 6.2
amazon:2023bpftool6.120
amazon:2023kernel6.12-tools0
amazon:2023kernel6.120
amazon:2023kernel6.12-libbpf0

Timeline

  • Dec 8, 2025 CVE Published
  • Dec 9, 2025 EPSS Score (30 in total, the first dated here)
  • Mar 29, 2026 Distribution Patch (114 in total, the first dated here)
  • Mar 29, 2026 Security Advisory (117 in total, the first dated here)
  • Jun 8, 2026 Coalition ESS Score

Query this with the API

The same record, from the CLI:

vulnetix vdb vuln CVE-2025-40329
vulnetix vdb fixes CVE-2025-40329

Or with curl, using the org id and key from your account page:

curl -s -H "Authorization: ApiKey ${VULNETIX_ORG_ID}:${VULNETIX_API_KEY}" \
  "https://api.vdb.vulnetix.com/v2/vuln/CVE-2025-40329/fixes/registry"

The Community plan is free and allows 50 queries a day. Get a free API key · API quickstart

References

Look up in the Resolve Platform →
$ Lookup Community · 50/day Open Lookup ›