Skip to content
Fencer Intel
no cvss —

CVE-2025-40329 json

drm/sched: Fix deadlock in drm_sched_entity_kill_jobs_cb

published 11mo ago modified 26d ago also EUVD-2025-201873

cvss
—
not scored
cisa kev
Not listed
not in CISA's catalog
epss
0.2%
EPSS 0.2% chance of exploitation in 30 days, percentile 15%
public exploits
0
none known

Summary

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]

Patch / fix

  • Linux Linux 6.6.117, 6.12.58, 6.17.8, 6.18
  • linux Debian 13 6.12.63-1
  • linux Debian 14 6.17.8-1

debian advisories DEBIAN-CVE-2025-40329

  • linux Ubuntu 24.04 LTS 6.8.0-106.106
  • linux Ubuntu 25.10 6.17.0-14.14
  • linux-aws Ubuntu 24.04 LTS 6.8.0-1050.53
  • linux-aws Ubuntu 25.10 6.17.0-1007.7
  • linux-gcp Ubuntu 24.04 LTS 6.8.0-1052.55
  • linux-gcp Ubuntu 25.10 6.17.0-1007.7
  • linux-gke Ubuntu 24.04 LTS 6.8.0-1048.53
  • linux-ibm Ubuntu 24.04 LTS 6.8.0-1049.49

ubuntu advisories UBUNTU-CVE-2025-40329

Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

  • kernel-rt Linux Micro 6.1, Linux Micro 6.0 6.4.0-40.1
  • kernel-source-rt Linux Micro 6.1, Linux Micro 6.0 6.4.0-40.1
  • kernel-source Linux Micro 6.1, Linux Micro 6.0 6.4.0-39.1
  • kernel-default Linux Micro 6.1, Linux Micro 6.0 6.4.0-39.1
  • kernel-kvmsmall Linux Micro 6.1, Linux Micro 6.0 6.4.0-39.1
  • kernel-default-base Linux Micro 6.1, Linux Micro 6.0 6.4.0-39.1.21.16
  • kernel-rt Linux Micro 6.2 6.12.0-160000.9.1
  • kernel-64kb SLES 16.0, Linux Micro 6.2, SLES for SAP applications 16.0 6.12.0-160000.9.1

suse advisories SUSE-SU-2026:20845-1SUSE-SU-2026:20876-1SUSE-SU-2026:20477-1SUSE-SU-2026:20498-1SUSE-SU-2026:20207-1SUSE-SU-2026:20220-1

  • kernel-rt openSUSE Leap 16.0 6.12.0-160000.9.1
  • dtb-aarch64 openSUSE Leap 16.0 6.12.0-160000.9.1
  • kernel-64kb openSUSE Leap 16.0 6.12.0-160000.9.1
  • kernel-syms openSUSE Leap 16.0 6.12.0-160000.9.1
  • kernel-azure openSUSE Leap 16.0 6.12.0-160000.9.1
  • kernel-obs-qa openSUSE Leap 16.0 6.12.0-160000.9.1
  • kernel-source openSUSE Leap 16.0 6.12.0-160000.9.1
  • kernel-default openSUSE Leap 16.0 6.12.0-160000.9.1

opensuse advisories openSUSE-SU-2026:20145-1

Is CVE-2025-40329 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2025-40329 updated cvss 5.8

kernel: drm/sched: Fix deadlock in drm_sched_entity_kill_jobs_cb

  • Red Hat Enterprise Linux 8 perf, kernel, bpftool, kernel-rt, kernel-core, kernel-tools, +29 more Red Hat Enterprise Linux 9 rv, perf, rtla, kernel, bpftool, libperf, +83 more Red Hat Enterprise Linux 10 kernel
    affected: no fix available “Fix deferred”
  • Red Hat Enterprise Linux 6 perf, kernel, python-perf, kernel-kdump, kernel-firmware, kernel-bootwrapper, +1 more Red Hat Enterprise Linux 7 perf, kernel, bpftool, kernel-rt, python-perf, kernel-kdump, +8 more
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

0.24% chance of exploitation in the next 30 days, higher than 15% of all scored CVEs (FIRST EPSS, 2026-11-09).

Affected products

  • Linux Linux

Classification

Technology feeds

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.