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-37854drm/amdkfd: Fix mode1 reset crash issue

Description

In the Linux kernel, the following vulnerability has been resolved: drm/amdkfd: Fix mode1 reset crash issue If HW scheduler hangs and mode1 reset is used to recover GPU, KFD signal user space to abort the processes. After process abort exit, user queues still use the GPU to access system memory before h/w is reset while KFD cleanup worker free system memory and free VRAM. There is use-after-free race bug that KFD allocate and reuse the freed system memory, and user queue write to the same system memory to corrupt the data structure and cause driver crash. To fix this race, KFD cleanup worker terminate user queues, then flush reset_domain wq to wait for any GPU ongoing reset complete, and then free outstanding BOs.

Timeline

  1. ID reserved

    By Linux

  2. · 23 days later

    Published

  3. · 15 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-37854, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1High7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
NVDNVD · Modified3.1High7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS (exploitation in 30 days)
0.27% · top 81% of all CVEs (19 Nov 2026)
Loading the EPSS history…

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

Affected products

  • Linux · Linux

    • affected a4c63cafa58b4bd9e15511bab77a4752b93d3aa0 – < 57c9dabda80ac167de8cd71231baae37cc2f442d
    • affected a4c63cafa58b4bd9e15511bab77a4752b93d3aa0 – < 89af6b39f028c130d4362f57042927f005423e6a
    • affected a4c63cafa58b4bd9e15511bab77a4752b93d3aa0 – < ffd37d7d44d7e0b6e769d4fe6590e327f8cc3951
    • affected a4c63cafa58b4bd9e15511bab77a4752b93d3aa0 – < 6f30a847432cae84c7428e9b684b3e3fa49b2391
    • affected a4c63cafa58b4bd9e15511bab77a4752b93d3aa0 – < 9c4bcdf4068aae3e17e31c144300be405cfa03ff
    • affected a4c63cafa58b4bd9e15511bab77a4752b93d3aa0 – < f0b4440cdc1807bb6ec3dce0d6de81170803569b
  • Linux · Linux

    • affected 5.18
    • unaffected < 5.18
    • unaffected 6.1.135 – ≤ 6.1.*
    • unaffected 6.6.88 – ≤ 6.6.*
    • unaffected 6.12.24 – ≤ 6.12.*
    • unaffected 6.13.12 – ≤ 6.13.*
    • unaffected 6.14.3 – ≤ 6.14.*
    • unaffected 6.15 – ≤ *

References

References7

Sources

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

Badge for a README or a ticket

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

Record last updated .