CVE-2025-38436
drm/scheduler: signal scheduled fence when kill job
In the Linux kernel, the following vulnerability has been resolved: drm/scheduler: signal scheduled fence when kill job When an entity from application B is killed, drm_sched_entity_kill() removes all jobs belonging to that entity through drm_sched_entity_kill_jobs_work(). If application A's job depends on a scheduled fence from application B's job, and that fence is not properly signaled during the killing process, application A's dependency cannot be cleared. This leads to application A hanging indefinitely while waiting for a dependency that will never be resolved. Fix this issue by ensuring that scheduled fences are properly signaled when an entity is killed, allowing dependent applications to continue execution.
Fixes and workarounds
No remediation reported in collected sources.
Missing remediation information is not evidence that no patch exists.
Affected products and versions
| Product | Versions | Authority |
|---|---|---|
| Linux Linux |
≥ a72ce6f84109c1dec1ab236d65979d3250668af3; < 8342127a8a65b0673863b106ce32b79c91ae3270 (affected, git) ≥ a72ce6f84109c1dec1ab236d65979d3250668af3; < c5734f9bab6f0d40577ad0633af4090a5fda2407 (affected, git) ≥ a72ce6f84109c1dec1ab236d65979d3250668af3; < aefd0a935625165a6ca36d0258d2d053901555df (affected, git) ≥ a72ce6f84109c1dec1ab236d65979d3250668af3; < aa382a8b6ed483e9812d0e63b6d1bdcba0186f29 (affected, git) ≥ a72ce6f84109c1dec1ab236d65979d3250668af3; < 471db2c2d4f80ee94225a1ef246e4f5011733e50 (affected, git) Other versions: unaffected |
CNA: Linux |
| Linux Linux |
4.3 (affected) ≥ 0; < 4.3 (unaffected, semver) ≥ 6.1.169; ≤ 6.1.* (unaffected, semver) ≥ 6.6.96; ≤ 6.6.* (unaffected, semver) ≥ 6.12.36; ≤ 6.12.* (unaffected, semver) ≥ 6.15.5; ≤ 6.15.* (unaffected, semver) ≥ 6.16; ≤ * (unaffected, original_commit_for_fix) Other versions: affected |
CNA: Linux |
Version ranges are source assertions. Check the vendor advisory and your installed configuration before determining exposure.
CVSS assessments
No CVSS assessment reported. An unscored record is not a low-severity determination.
Exploit evidence
No exploit evidence in collected sources. This is not proof of no exploitation.
References
- https://git.kernel.org/stable/c/8342127a8a65b0673863b106ce32b79c91ae3270CNA: Linux
- https://git.kernel.org/stable/c/c5734f9bab6f0d40577ad0633af4090a5fda2407CNA: Linux
- https://git.kernel.org/stable/c/aefd0a935625165a6ca36d0258d2d053901555dfCNA: Linux
- https://git.kernel.org/stable/c/aa382a8b6ed483e9812d0e63b6d1bdcba0186f29CNA: Linux
- https://git.kernel.org/stable/c/471db2c2d4f80ee94225a1ef246e4f5011733e50CNA: Linux
For agents and automation
Read public disclosures for free as Markdown or JSON. Compatible browsers also expose native WebMCP tools to search disclosures, read this page, and discover API access.
Use the ontology-linked Cyber API with x402 pay per request, or a Y2 Pro or Elite API key with the intel:cyber scope.
Endpoints and access details
https://api.y2.dev/api/v2/cyber/cveshttps://api.y2.dev/api/v2/cyber/cves/{cveId}
A workspace owner or admin can create a Pro or Elite API key. Send Authorization: Bearer <Y2_API_KEY> from your trusted agent runtime.
For x402, omit Authorization and read the HTTP 402 payment challenge before signing a retry. Public browser tools do not make payments.