CVE-2025-38041: clk: sunxi-ng: h616: Reparent GPU clock during frequency changes
Noroxi assessment
Priority: Monitor (action score 22/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.23% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 0c4f89f02c72f7cfb98a9a09cae89cc2e39e6017, 1439673b78185eaaa5fae444b3a9d58c434ee78e, 47a0da0c80749767de1bc0a7a27a69b34c22fbda.
Low priority for now. Upgrade to Linux Linux 0c4f89f02c72f7cfb98a9a09cae89cc2e39e6017, 1439673b78185eaaa5fae444b3a9d58c434ee78e, 47a0da0c80749767de1bc0a7a27a69b34c22fbda or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Jun 18, 2025
- Updated
- Oct 30, 2026
- EPSS
- 0.2% · 14th percentile
- CWE
- —
Report tools
Action score
22
Low priority for now.
- CVSS
- 22 / 40 · 5.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 5.12affected
- 88dde5e23da1a16fe9a417171e6c941736b8d3a6 and later · before 5b447255bf170aee508d50c4a3a1156eb6dcc9b4affected · git
- 88dde5e23da1a16fe9a417171e6c941736b8d3a6 and later · before 47a0da0c80749767de1bc0a7a27a69b34c22fbdaaffected · git
- 88dde5e23da1a16fe9a417171e6c941736b8d3a6 and later · before 0c4f89f02c72f7cfb98a9a09cae89cc2e39e6017affected · git
- 88dde5e23da1a16fe9a417171e6c941736b8d3a6 and later · before 1439673b78185eaaa5fae444b3a9d58c434ee78eaffected · git
- 88dde5e23da1a16fe9a417171e6c941736b8d3a6 and later · before eb963d7948ce6571939c6875424b557b25f16610affected · git
- before 5.12not affected · semver
- 6.1.191 and later · up to and including 6.1.*not affected · semver
- 6.6.160 and later · up to and including 6.6.*not affected · semver
- 6.12.114 and later · up to and including 6.12.*not affected · semver
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernelbefore 6.14.9
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | from 0 | — |
| Debian:13 | linux | before 6.12.115-2 | 6.12.115-2 |
| Debian:14 | linux | before 6.16.3-1 | 6.16.3-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV90Now
- CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe…KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
Published before and after this one in the same product
- ← EarlierCVE-2025-38039Jun 18, 2025 · net/mlx5e: Avoid WARN_ON when configuring MQPRIO with HTB offload enabled22Monitor
- ← EarlierCVE-2025-38040Jun 18, 2025 · serial: mctrl_gpio: split disable_ms into sync and no_sync APIs22Monitor
- Later →CVE-2025-38042Jun 18, 2025 · dmaengine: ti: k3-udma-glue: Drop skip_fdq argument from k3_udma_glue_reset_rx_chn22Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 0c4f89f02c72f7cfb98a9a09cae89cc2e39e6017 | Vendor (CNA) |
| Linux Linux | 1439673b78185eaaa5fae444b3a9d58c434ee78e | Vendor (CNA) |
| Linux Linux | 47a0da0c80749767de1bc0a7a27a69b34c22fbda | Vendor (CNA) |
| Linux Linux | 5b447255bf170aee508d50c4a3a1156eb6dcc9b4 | Vendor (CNA) |
| Linux Linux | eb963d7948ce6571939c6875424b557b25f16610 | Vendor (CNA) |
| debian:linux | 6.12.115-2 · Debian:13 | Package registry (OSV) |
| debian:linux | 6.16.3-1 · Debian:14 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
—
CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (4 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.