Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2025-38436drm/scheduler: signal scheduled fence when kill job

Description

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.

Timeline

  1. ID reserved

    By Linux

  2. · 3 months later

    Published

  3. · 16 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2025-38436, by who scored it
Scored byCVSSScoreVector
NVDNVD · Modified3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.16% · top 94% of all CVEs (15 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.

Affected products

  • Linux · Linux

    • affected a72ce6f84109c1dec1ab236d65979d3250668af3 – < 8342127a8a65b0673863b106ce32b79c91ae3270
    • affected a72ce6f84109c1dec1ab236d65979d3250668af3 – < c5734f9bab6f0d40577ad0633af4090a5fda2407
    • affected a72ce6f84109c1dec1ab236d65979d3250668af3 – < aefd0a935625165a6ca36d0258d2d053901555df
    • affected a72ce6f84109c1dec1ab236d65979d3250668af3 – < aa382a8b6ed483e9812d0e63b6d1bdcba0186f29
    • affected a72ce6f84109c1dec1ab236d65979d3250668af3 – < 471db2c2d4f80ee94225a1ef246e4f5011733e50
  • Linux · Linux

    • affected 4.3
    • unaffected < 4.3
    • unaffected 6.1.169 – ≤ 6.1.*
    • unaffected 6.6.96 – ≤ 6.6.*
    • unaffected 6.12.36 – ≤ 6.12.*
    • unaffected 6.15.5 – ≤ 6.15.*
    • unaffected 6.16 – ≤ *

References

References5

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2025-38436 badge
[![CVE-2025-38436](https://cveledger.app/badge/CVE-2025-38436.svg)](https://cveledger.app/cve/CVE-2025-38436)

Record last updated .