CVE-2025-38436: Linux kernel · drm/scheduler: signal scheduled fence when kill job
Affects Linux kernelSource CVE Database V5
Not known to be exploited · fixed in c5734f9bab6f0d40577ad0633af4090a5fda2407 : update Linux kernel when convenient.
Data as of 5 Nov 2026, 21:20 UTC
Rated Medium by Threat Radar's AI analysis · No CVSS score from NVD or the CNA
Thin evidence
One scorer or none- CISA SSVC
- Exploitation
- No evidence of active exploitation and no public proof of concept
- Automatable
- Attackers cannot reliably automate steps 1–4 of the kill chain
- Technical impact
- Limited control over the software or limited information exposure
CISA SSVC assessment, 2026-11-05.
- Patch
- Available – fixed in c5734f9bab6f0d40577ad0633af4090a5fda2407, aefd0a935625165a6ca36d0258d2d053901555df, aa382a8b6ed483e9812d0e63b6d1bdcba0186f29 +2
Exploitation evidence
Disclosed: evidence found.
CVE published 25 Jul 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: 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 5 Nov 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in– |
AI-suggested
This vulnerability has been fixed in specific Linux kernel commits. Users should update to a kernel version including these fixes to resolve the issue. No additional mitigation is required once the fix is applied.
Description
A vulnerability in the Linux kernel's DRM scheduler causes dependent applications to hang indefinitely when a job is killed without properly signaling its scheduled fence. This occurs because the scheduled fence from the killed job is not signaled, leaving dependent jobs waiting forever. The issue affects Linux kernel version 4.3 and has been fixed in later commits.
References
- git.kernel.org/stable/c/8342127a8a65b0673863b106ce32b79c91ae3270 (opens in a new tab)
- git.kernel.org/stable/c/c5734f9bab6f0d40577ad0633af4090a5fda2407 (opens in a new tab)
- git.kernel.org/stable/c/aefd0a935625165a6ca36d0258d2d053901555df (opens in a new tab)
- git.kernel.org/stable/c/aa382a8b6ed483e9812d0e63b6d1bdcba0186f29 (opens in a new tab)
- git.kernel.org/stable/c/471db2c2d4f80ee94225a1ef246e4f5011733e50 (opens in a new tab)