CVE-2025-38521 Details
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.
A vulnerability in the Linux kernel's GPU hard reset sequence can lead to a kernel crash. This issue arises in the DRM (Direct Rendering Manager) subsystem for Imagination GPUs. The hard reset process improperly uses the 'pm_runtime_force_suspend()' and 'pm_runtime_force_resume()' functions, which should only be applied during system-wide power management transitions. Depending on the internal runtime power management state, 'pm_runtime_force_resume()' may not reactivate the GPU unless necessary. If this occurs, the expected resume callback is not triggered, leaving the GPU clocks disabled. The kernel then crashes when it tries to access GPU registers during the power-on sequence. The vulnerability has been addressed by replacing the problematic power management calls with direct references to the driver's specific power management callbacks, ensuring the GPU clocks are properly re-enabled and preventing the kernel crash.
Users can upgrade to the latest version of the Linux kernel where this vulnerability has been fixed. Instructions for downloading the patched version are available on the official Linux kernel website.
Metrics
CVSS 4.0 Severity and Vector Strings:
No CVSS 4.0 data is available for this CVE.
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
CISA-ADP
Assessed Nov 5, 2026References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
| URL | Source(s) | Tag(s) |
|---|---|---|
| https://git.kernel.org/stable/c/9f852d301f642223c4798f3c13ba15e91165d078 | kernel.org | Patch |
| https://git.kernel.org/stable/c/d38376b3ee48d073c64e75e150510d7e6b4b04f7 | kernel.org | Patch |
| https://git.kernel.org/stable/c/e066cc6e0f094ca2120f1928d126d56f686cd73e | kernel.org | Patch |
Weakness Enumeration
| CWE-ID | CWE Name | Source |
|---|---|---|
| CWE-668 | Exposure of Resource to Wrong Sphere | [email protected] |
Affected Products
| Product | Versions |
|---|---|
| linux linux kernel | >= 6.8, < 6.12.39 >= 6.13, < 6.15.7 6.16 rc1 6.16 rc2 6.16 rc3 6.16 rc4 6.16 rc5 |
CPE
Remediation
| |
Change History
5 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Nov 5, 2026 | CVE Modified | kernel.org |
| Nov 5, 2026 | CVE Modified | CISA-ADP |
| Jun 17, 2026 | CVE Modified | kernel.org |
| Jan 22, 2026 | Initial Analysis | [email protected] |
| Aug 16, 2025 | New CVE Received | kernel.org |