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-38521drm/imagination: Fix kernel crash when hard resetting the GPU

Description

In the Linux kernel, the following vulnerability has been resolved: drm/imagination: Fix kernel crash when hard resetting the GPU The GPU hard reset sequence calls pm_runtime_force_suspend() and pm_runtime_force_resume(), which according to their documentation should only be used during system-wide PM transitions to sleep states. The main issue though is that depending on some internal runtime PM state as seen by pm_runtime_force_suspend() (whether the usage count is <= 1), pm_runtime_force_resume() might not resume the device unless needed. If that happens, the runtime PM resume callback pvr_power_device_resume() is not called, the GPU clocks are not re-enabled, and the kernel crashes on the next attempt to access GPU registers as part of the power-on sequence. Replace calls to pm_runtime_force_suspend() and pm_runtime_force_resume() with direct calls to the driver's runtime PM callbacks, pvr_power_device_suspend() and pvr_power_device_resume(), to ensure clocks are re-enabled and avoid the kernel crash.

Timeline

  1. ID reserved

    By Linux

  2. · 4 months 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-38521, by who scored it
Scored byCVSSScoreVector
NVDNVD · Analyzed3.1High7.1CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H
EPSS (exploitation in 30 days)
0.18% · top 93% of all CVEs (18 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: High 7.1.

Affected products

  • Linux · Linux

    • affected cc1aeedb98ad347c06ff59e991b2f94dfb4c565d – < 9f852d301f642223c4798f3c13ba15e91165d078
    • affected cc1aeedb98ad347c06ff59e991b2f94dfb4c565d – < e066cc6e0f094ca2120f1928d126d56f686cd73e
    • affected cc1aeedb98ad347c06ff59e991b2f94dfb4c565d – < d38376b3ee48d073c64e75e150510d7e6b4b04f7
  • Linux · Linux

    • affected 6.8
    • unaffected < 6.8
    • unaffected 6.12.39 – ≤ 6.12.*
    • unaffected 6.15.7 – ≤ 6.15.*
    • unaffected 6.16 – ≤ *

References

References3

Sources

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

Badge for a README or a ticket

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

Record last updated .