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

Published Aug 16, 2025
·
Updated

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 pmruntimeforcesuspend() and pmruntimeforceresume(), 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 pmruntimeforcesuspend() (whether the usage count is <= 1), pmruntimeforceresume() might not resume the device unless needed. If that happens, the runtime PM resume callback pvrpowerdeviceresume() 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 pmruntimeforcesuspend() and pmruntimeforceresume() with direct calls to the driver's runtime PM callbacks, pvrpowerdevicesuspend() and pvrpowerdeviceresume(), to ensure clocks are re-enabled and avoid the kernel crash.

Affected Software

8 affected components
Linux Linux kernel
Linux Linux kernel>=6.8<6.12.39
Linux Linux kernel>=6.13<6.15.7
Linux Linux kernel=6.16-rc1
Linux Linux kernel=6.16-rc2
Linux Linux kernel=6.16-rc3
Linux Linux kernel=6.16-rc4
Linux Linux kernel=6.16-rc5

Event History

Aug 16, 2025
CVE Published
via MITRE·10:55 AM
Data Sourced
via MITRE·10:55 AM
Description
Data Sourced
via NVD·11:15 AM
RemedyDescriptionSeverityWeaknessAffected Software

Frequently Asked Questions

1

What is the severity of CVE-2025-38521?

The severity of CVE-2025-38521 is considered to be critical due to its impact on kernel stability and potential denial of service.

2

How do I fix CVE-2025-38521?

To fix CVE-2025-38521, ensure that your Linux kernel is updated to the latest available version where this vulnerability has been patched.

3

Which versions of the Linux kernel are affected by CVE-2025-38521?

CVE-2025-38521 affects multiple versions of the Linux kernel that are prior to the release of the patch addressing this issue.

4

What are the consequences of not addressing CVE-2025-38521?

Not addressing CVE-2025-38521 can lead to kernel crashes, system instability, and denial of service for applications relying on GPU functionality.

5

Is CVE-2025-38521 related to GPU functionality in the Linux kernel?

Yes, CVE-2025-38521 specifically relates to a vulnerability that affects the GPU hard reset sequence in the Linux kernel.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203