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-38515drm/sched: Increment job count before swapping tail spsc queue

Description

In the Linux kernel, the following vulnerability has been resolved: drm/sched: Increment job count before swapping tail spsc queue A small race exists between spsc_queue_push and the run-job worker, in which spsc_queue_push may return not-first while the run-job worker has already idled due to the job count being zero. If this race occurs, job scheduling stops, leading to hangs while waiting on the job’s DMA fences. Seal this race by incrementing the job count before appending to the SPSC queue. This race was observed on a drm-tip 6.16-rc1 build with the Xe driver in an SVM test case.

Timeline

  1. ID reserved

    By Linux

  2. · 4 months later

    Published

  3. · 9 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-38515, by who scored it
Scored byCVSSScoreVector
NVDNVD · Analyzed3.1Medium4.7CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.17% · top 93% of all CVEs (15 Nov 2026)
Loading the EPSS history…

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

Affected products

  • Linux · Linux

    • affected 27105db6c63a571b91d01e749d026105a1e63bcf – < 549a9c78c3ea6807d0dc4162a4f5ba59f217d5a0
    • affected 27105db6c63a571b91d01e749d026105a1e63bcf – < e62f51d0ec8a9baf324caf9a564f8e318d36a551
    • affected 27105db6c63a571b91d01e749d026105a1e63bcf – < ef841f8e4e1ff67817ca899bedc5ebb00847c0a7
    • affected 27105db6c63a571b91d01e749d026105a1e63bcf – < f9a4f28a4fc4ee453a92a9abbe36e26224d17749
    • affected 27105db6c63a571b91d01e749d026105a1e63bcf – < c64f5310530baf75328292f9b9f3f2961d185183
    • affected 27105db6c63a571b91d01e749d026105a1e63bcf – < e2d6547dc8b9b332f9bc00875197287a6a4db65a
    • affected 27105db6c63a571b91d01e749d026105a1e63bcf – < ef58a95457466849fa7b31fd3953801a5af0f58b
    • affected 27105db6c63a571b91d01e749d026105a1e63bcf – < 8af39ec5cf2be522c8eb43a3d8005ed59e4daaee
  • Linux · Linux

    • affected 4.16
    • unaffected < 4.16
    • unaffected 5.4.296 – ≤ 5.4.*
    • unaffected 5.10.240 – ≤ 5.10.*
    • unaffected 5.15.189 – ≤ 5.15.*
    • unaffected 6.1.146 – ≤ 6.1.*
    • unaffected 6.6.99 – ≤ 6.6.*
    • unaffected 6.12.39 – ≤ 6.12.*
    • unaffected 6.15.7 – ≤ 6.15.*
    • unaffected 6.16 – ≤ *

References

References10

Sources

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

Badge for a README or a ticket

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

Record last updated .