LiveActive security incident?Get immediate response
CVE Record

CVE-2025-38521: drm/imagination: Fix kernel crash when hard resetting the GPU

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.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This Linux kernel issue can crash systems using the Imagination GPU driver during a GPU hard reset. The flaw is operationally serious for affected devices because it can disrupt availability, but the sources do not provide CVSS, confirmed exploitability, or evidence of active exploitation.

Executive priority

Treat as a targeted availability issue, not a broad internet-facing emergency based on current evidence. Patch affected Linux GPU systems through normal kernel update channels, with higher priority for production devices where GPU resets could interrupt service.

Technical view

The drm/imagination hard reset path used runtime PM force suspend and resume helpers outside their intended system-wide sleep context. In some runtime PM states, resume may not re-enable GPU clocks, causing a kernel crash when GPU registers are next accessed. Stable kernel commits replace those calls with direct driver runtime PM callbacks.

Likely exposure

Exposure appears limited to Linux systems running affected kernel versions with the drm/imagination GPU driver in use. The provided affected-version data is incomplete and should be validated against distribution kernel packages and the referenced stable commits.

Exploitation context

The source bundle does not report active exploitation, public exploit code, or KEV listing. The described impact is a kernel crash during GPU hard reset handling, suggesting availability risk where this GPU driver and reset path are reachable.

Researcher notes

Evidence supports a kernel crash caused by incorrect runtime PM helper use in the Imagination GPU reset path. The bundle lacks CVSS, CWE, exploit prerequisites, and complete product mapping, so validation should focus on driver presence, kernel lineage, and stable commit inclusion.

Mitigation direction

  • Apply vendor or distribution kernel updates containing the referenced stable fixes.
  • Prioritize systems using Imagination GPUs or the drm/imagination kernel driver.
  • If updates are unavailable, monitor vendor guidance for temporary mitigations.
  • Avoid assuming unaffected status from upstream version numbers alone; check distro backports.

Validation and detection

  • Inventory Linux systems using the drm/imagination or PVR GPU driver.
  • Confirm running kernels include one of the referenced stable commits or distro backports.
  • Review kernel logs for GPU hard reset crashes or register-access faults.
  • Track CVE-2025-38521 in vulnerability management until package mapping is confirmed.
Prepared
Confidence
medium
Sources
5

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2025-38521 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
3Timeline events
0ADP providers
4Source links

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxcc1aeedb98ad347c06ff59e991b2f94dfb4c565d, cc1aeedb98ad347c06ff59e991b2f94dfb4c565d, cc1aeedb98ad347c06ff59e991b2f94dfb4c565dunaffected
LinuxLinux6.8, 0, 6.12.39, 6.15.7, 6.16affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.