GPU denial of service via unsafe PLL retuning
Published Jun 18, 2025 · Updated May 11, 2026
Denial of service in the Linux H616 clock driver from 5.12 through 6.14.8 allows local users to hang the GPU via device DVFS. The driver retunes the H616 GPU PLL in place even though the PLL lacks documented dynamic-frequency support, instead of temporarily reparenting GPU0 to GPU1. Exploitation requires local access to an H616 system using Panfrost and GPU DVFS; the bounded consequence is kernel oopses and a GPU hang.
Summary
What happened
Denial of service in the Linux H616 clock driver from 5.12 through 6.14.8 allows local users to hang the GPU via device DVFS. The driver retunes the H616 GPU PLL in place even though the PLL lacks documented dynamic-frequency support, instead of temporarily reparenting GPU0 to GPU1. Exploitation requires local access to an H616 system using Panfrost and GPU DVFS; the bounded consequence is kernel oopses and a GPU hang.
The record
- CVE
- CVE-2025-38041
- Published
- Jun 18, 2025
- Updated
- May 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 18, 2025CVE publishedPublication date reported by the CVE source.
- May 11, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=5.12
- Affected versionversion=88dde5e23da1a16fe9a417171e6c941736b8d3a6 <1439673b78185eaaa5fae444b3a9d58c434ee78e
- Affected versionversion=88dde5e23da1a16fe9a417171e6c941736b8d3a6 <eb963d7948ce6571939c6875424b557b25f16610
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo