CVE-2025-38041 — clk: sunxi-ng: h616: Reparent GPU clock during frequency changes
In the Linux kernel, the following vulnerability has been resolved: clk: sunxi-ng: h616: Reparent GPU clock during frequency changes The H616 manual does not state that the GPU PLL supports dynamic frequency configuration, so we must take extra care when changing the frequency. Currently any attempt to do device DVFS on the GPU lead to panfrost various ooops, and GPU hangs. The manual describes the algorithm for changing the PLL frequency, which the CPU PLL notifier code already support, so we reuse that to reparent the GPU clock to GPU1 clock during frequency changes.
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- EPSS 0.2% (30-day exploitation probability)+2
- Technical severity (medium)+3
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
- Documented patch — git.kernel.org (NIST National Vulnerability Database)
- Documented patch — git.kernel.org (NIST National Vulnerability Database)
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (Linux Linux, Linux Linux Kernel).
- Apply the fixed version or the patch documented under Remediation.
- Search available logs for exploit probes, errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| Linux | Linux | ≥ 88dde5e23da1a16fe9a417171e6c941736b8d3a6 and < 47a0da0c80749767de1bc0a7a27a69b34c22fbda≥ 88dde5e23da1a16fe9a417171e6c941736b8d3a6 and < 0c4f89f02c72f7cfb98a9a09cae89cc2e39e6017≥ 88dde5e23da1a16fe9a417171e6c941736b8d3a6 and < 1439673b78185eaaa5fae444b3a9d58c434ee78e≥ 88dde5e23da1a16fe9a417171e6c941736b8d3a6 and < eb963d7948ce6571939c6875424b557b25f16610version 5.12 | Vulnerable | CVE Program (cve.org) e CISA ADP |
| Linux | Linux Kernel | < 6.14.9 | Vulnerable | NIST National Vulnerability Database |
Attack characteristics
The CVSS vector, decoded. It describes the attack, not your exposure to it.
Every base score collected
Sources score independently and may disagree; each row says who scored it and under which version.
| Score | Version | Severity | Expl. | Impact | Scored by |
|---|---|---|---|---|---|
| 5.5 | CVSS 3.1 | Medium | 1.8 | 3.6 | nvd@nist.gov via NIST National Vulnerability Database |
| 5.5 | CVSS 3.1 | Medium | — | — | GitHub, Inc. via GitHub Security Advisories |
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H (score shown at the top: nvd@nist.gov) EPSS over time FIRST
Oct 20, 2026 → Oct 28, 2026 · 9 reading(s) · max 0.24%
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Local/physical vector: focus on endpoint telemetry (EDR) from affected hosts.
Timeline
What happened to this CVE, newest first.
- 2026
- Affected products added · linux/linux
- Record published
- Fix documented
- Affected products added · linux/linux kernel
- CVSS changed · 5.5
- Source status changed · → Modified
- Record created in this database
- 2025
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 2× References added · Oct 21, 2026 – Oct 21, 2026
- 1× Official description updated · Oct 21, 2026 – Oct 21, 2026
References
6 on the record
- git.kernel.org/stable/c/1439673b78185eaaa5fae444b3a9d58c434ee78e
- git.kernel.org/stable/c/eb963d7948ce6571939c6875424b557b25f16610
- git.kernel.org/stable/c/47a0da0c80749767de1bc0a7a27a69b34c22fbda
- nvd.nist.gov/vuln/detail/CVE-2025-38041
- github.com/advisories/GHSA-84x2-rfrf-6f2c
- git.kernel.org/stable/c/0c4f89f02c72f7cfb98a9a09cae89cc2e39e6017
Elsewhere on this site
Related CVEs (same products)
- Unknown CVE-2026-99216 Drivers: hv: Don't reset VMBus connection state on error/exit paths 17h
- Unknown CVE-2026-99215 power: supply: core: prevent unregistering a power supply while a callback runs 17h
- Unknown CVE-2026-99207 scsi: target: Disable interrupts while holding delayed_cmd_lock 17h
- Unknown CVE-2026-99208 drm/xe/oa: Zero OA buffer at allocation 17h
- Unknown CVE-2026-99209 drm/xe: skip eviction of a BO with no resource 17h
- Unknown CVE-2026-99210 accel/rocket: clear rdev on device init failure 17h
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No CISA SSVC assessment.
- No CWE classification.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2025-38041 is "clk: sunxi-ng: h616: Reparent GPU clock during frequency changes", rated Medium. It affects Linux (Linux); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 5.5 describes technical severity. EPSS 0.24% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.