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-37951drm/v3d: Add job to pending list if the reset was skipped

Description

In the Linux kernel, the following vulnerability has been resolved: drm/v3d: Add job to pending list if the reset was skipped When a CL/CSD job times out, we check if the GPU has made any progress since the last timeout. If so, instead of resetting the hardware, we skip the reset and let the timer get rearmed. This gives long-running jobs a chance to complete. However, when `timedout_job()` is called, the job in question is removed from the pending list, which means it won't be automatically freed through `free_job()`. Consequently, when we skip the reset and keep the job running, the job won't be freed when it finally completes. This situation leads to a memory leak, as exposed in [1] and [2]. Similarly to commit 704d3d60fec4 ("drm/etnaviv: don't block scheduler when GPU is still active"), this patch ensures the job is put back on the pending list when extending the timeout.

Timeline

  1. ID reserved

    By Linux

  2. · 34 days later

    Published

  3. · 12 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-37951, by who scored it
Scored byCVSSScoreVector
NVDNVD · Analyzed3.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.19% · top 91% of all CVEs (14 Nov 2026)
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 57692c94dcbe99a1e0444409a3da13fb3443562c – < 5235b56b7e5449d990d21d78723b1a5e7bb5738e
    • affected 57692c94dcbe99a1e0444409a3da13fb3443562c – < 12125f7d9c15e6d8ac91d10373b2db2f17dcf767
    • affected 57692c94dcbe99a1e0444409a3da13fb3443562c – < a5f162727b91e480656da1876247a91f651f76de
    • affected 57692c94dcbe99a1e0444409a3da13fb3443562c – < 422a8b10ba42097a704d6909ada2956f880246f2
    • affected 57692c94dcbe99a1e0444409a3da13fb3443562c – < 35e4079bf1a2570abffce6ababa631afcf8ea0e5
  • Linux · Linux

    • affected 4.18
    • unaffected < 4.18
    • unaffected 6.1.139 – ≤ 6.1.*
    • unaffected 6.6.91 – ≤ 6.6.*
    • unaffected 6.12.29 – ≤ 6.12.*
    • unaffected 6.14.7 – ≤ 6.14.*
    • unaffected 6.15 – ≤ *

References

References6

Sources

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

Badge for a README or a ticket

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

Record last updated .