CVE-2025-68318: clk: thead: th1520-ap: set all AXI clocks to CLK_IS_CRITICAL
Noroxi assessment
Priority: Monitor (action score 0/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.21% (FIRST EPSS).
- Fixed version: Linux Linux bdec5e01fc2f3114d1fb1daeb1000911d783c4ae, c567bc5fc68c4388c00e11fc65fd14fe86b52070, d816c00bb69fb2eecd3fccac067857f3a0dbc44e.
Low priority for now. Upgrade to Linux Linux bdec5e01fc2f3114d1fb1daeb1000911d783c4ae, c567bc5fc68c4388c00e11fc65fd14fe86b52070, d816c00bb69fb2eecd3fccac067857f3a0dbc44e 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: thead: th1520-ap: set all AXI clocks to CLK_IS_CRITICAL The AXI crossbar of TH1520 has no proper timeout handling, which means gating AXI clocks can easily lead to bus timeout and thus system hang. Set all AXI clock gates to CLK_IS_CRITICAL. All these clock gates are ungated by default on system reset. In addition, convert all current CLK_IGNORE_UNUSED usage to CLK_IS_CRITICAL to prevent unwanted clock gating.
- Published
- Dec 16, 2025
- Updated
- Oct 21, 2026
- EPSS
- 0.2% · 11th percentile
- CWE
- —
Report tools
Action score
0
Low priority for now.
- CVSS
- 0 / 40 · —
- 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.
—
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
- 6.11affected
- ae81b69fd2b1eb4885b352749b1fd1172e2f0f18 and later · before d816c00bb69fb2eecd3fccac067857f3a0dbc44eaffected · git
- ae81b69fd2b1eb4885b352749b1fd1172e2f0f18 and later · before bdec5e01fc2f3114d1fb1daeb1000911d783c4aeaffected · git
- ae81b69fd2b1eb4885b352749b1fd1172e2f0f18 and later · before c567bc5fc68c4388c00e11fc65fd14fe86b52070affected · git
- before 6.11not affected · semver
- 6.12.114 and later · up to and including 6.12.*not affected · semver
- 6.17.8 and later · up to and including 6.17.*not affected · semver
- 6.18 and laternot affected · original_commit_for_fix
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-6.12 | before 6.12.115-2~deb12u1 | 6.12.115-2~deb12u1 |
| Debian:13 | linux | before 6.12.115-2 | 6.12.115-2 |
| Debian:14 | linux | before 6.17.8-1 | 6.17.8-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2025-68316Dec 16, 2025 · scsi: ufs: core: Fix invalid probe error return value0Monitor
- ← EarlierCVE-2025-68317Dec 16, 2025 · io_uring/zctx: check chained notif contexts31Monitor
- Later →CVE-2025-68319Dec 16, 2025 · netconsole: Acquire su_mutex before navigating configs hierarchy0Monitor
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 | bdec5e01fc2f3114d1fb1daeb1000911d783c4ae | Vendor (CNA) |
| Linux Linux | c567bc5fc68c4388c00e11fc65fd14fe86b52070 | Vendor (CNA) |
| Linux Linux | d816c00bb69fb2eecd3fccac067857f3a0dbc44e | Vendor (CNA) |
| debian:linux | 6.12.115-2 · Debian:13 | Package registry (OSV) |
| debian:linux | 6.17.8-1 · Debian:14 | Package registry (OSV) |
| debian:linux-6.12 | 6.12.115-2~deb12u1 · Debian:12 | 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
No CVSS vector for this record, so attack conditions can't be derived.
Weakness class (CWE)
—
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 (2 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.