VulnerabilityPublished 9 Dec 2025Updated 31 Jul 2026

CVE-2025-40329: Linux kernel · drm/sched: Fix deadlock in drm_sched_entity_kill_jobs_cb

Affects Linux kernelSource GCVE Database

Not known to be exploited · fixed in 6.8.0-1050.53~22.04.1 : update Linux kernel when convenient.

Data as of 26 Oct 2026, 14:05 UTC

Severity

Medium

Rated by Threat Radar · No CVSS score from NVD or the CNA

EPSS: 0.2% chance of exploitation in 30 days – higher than 12% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 6.8.0-1050.53~22.04.1, 6.8.0-1051.57~22.04.1, 6.8.0-1052.55~22.04.1 +35

Exploitation evidence

Disclosed: evidence found.
CVE published 9 Dec 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

Product	Affected	Fixed in
Ubuntu 25.10linux`pkg:deb/ubuntu/linux@6.17.0-14.14?arch=source&distro=questing`Other threats	Affected <6.17.0-14.14	Fixed in 6.17.0-14.14
Ubuntu 25.10linux-aws`pkg:deb/ubuntu/linux-aws@6.17.0-1007.7?arch=source&distro=questing`Other threats	Affected <6.17.0-1007.7	Fixed in 6.17.0-1007.7
Ubuntu 25.10linux-azure`pkg:deb/ubuntu/linux-azure@6.17.0-1008.8?arch=source&distro=questing`Other threats	Affected <6.17.0-1008.8	Fixed in 6.17.0-1008.8
Ubuntu 25.10linux-azure-fde`pkg:deb/ubuntu/linux-azure-fde@6.17.0-1017.17?arch=source&distro=questing`Other threats	Affected 6.17.0-1003.3 – 6.17.0-1017.17 10 affected builds	Fixed in–
Ubuntu 25.10linux-gcp`pkg:deb/ubuntu/linux-gcp@6.17.0-1007.7?arch=source&distro=questing`Other threats	Affected <6.17.0-1007.7	Fixed in 6.17.0-1007.7
Ubuntu 25.10linux-oracle`pkg:deb/ubuntu/linux-oracle@6.17.0-1007.7?arch=source&distro=questing`Other threats	Affected <6.17.0-1007.7	Fixed in 6.17.0-1007.7

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A patch is available and should be applied to affected Linux kernel versions. The vendor advisory from Ubuntu confirms that this issue is fixed in updated kernel packages. Users should update to the fixed kernel versions as provided by their distribution. No additional mitigation steps are required beyond applying the official fix.

Description

A deadlock vulnerability in the Linux kernel's DRM scheduler subsystem (drm_sched_entity_kill_jobs_cb) has been resolved. The issue involves interrupt-unsafe locking scenarios that can cause deadlocks when accessing job dependencies and handling fence locks in interrupt context. The fix moves the code iterating on dependencies and re-arming them out of the interrupt context to prevent deadlocks. This vulnerability affects multiple specific Linux kernel versions and has been addressed in official updates.

Impact

An attacker could potentially exploit this deadlock vulnerability to cause system instability or denial of service by triggering deadlocks in the DRM scheduler subsystem. This could impact system reliability and availability but does not indicate direct code execution or privilege escalation.

Summary

The vulnerability in the Linux kernel's DRM scheduler (drm_sched_entity_kill_jobs_cb) arises from a deadlock caused by improper locking order and interrupt-unsafe locking. Specifically, CPU0 holds the xa_lock while accessing job dependencies without disabling interrupts, while CPU1 executes drm_sched_entity_kill_jobs_cb in interrupt context and attempts to acquire the same lock, causing a deadlock. Additionally, dma_fence_signal and dma_fence_add_callback locking order can cause deadlocks if they share the same spinlock. The fix involves replacing xa_* functions with their interrupt-safe counterparts and moving dependency iteration and re-arming to a workqueue context (drm_sched_entity_kill_jobs_work) to avoid deadlocks.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 25 Oct 2026, 14:16 UTC

Technical details

References

Community reviews

Related threats