# CVE-2025-68318: clk: thead: th1520-ap: set all AXI clocks to CLK_IS_CRITICAL

> A missing critical clock flag in the TH1520 AXI driver allows clock gating to cause bus timeouts, leading to system hangs and denial of service.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Not stated
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 16 Dec 2025
- **Updated:** 21 Oct 2026
- **Also known as:** BELL-CVE-2025-68318, DEBIAN-CVE-2025-68318, GHSA-35v6-xwx8-cj7m, ROOT-OS-DEBIAN-13-CVE-2025-68318, ROOT-OS-UBUNTU-2204-CVE-2025-68318, ROOT-OS-UBUNTU-2404-CVE-2025-68318, UBUNTU-CVE-2025-68318

## What is CVE-2025-68318?

CVE-2025-68318 is a denial of service vulnerability in Linux, published on 16 Dec 2025. 

### Official description

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.

## Which versions are affected by CVE-2025-68318?


## How do I fix CVE-2025-68318?

Apply the vendor's patch.

## Is CVE-2025-68318 being exploited?

There is no known exploitation of CVE-2025-68318 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-68318 and fix it if it is affected.

What it is: CVE-2025-68318 is a denial of service vulnerability in Linux, published on 16 Dec 2025. 
Exploitation: There is no known exploitation of CVE-2025-68318 in the wild and no public exploit code.

Affected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-68318/ (Markdown: https://insights.sbomify.com/CVE-2025-68318/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-68318
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-68318
- OSV: https://osv.dev/vulnerability/CVE-2025-68318

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-68318/
Summaries are generated and may contain mistakes; the official description above is the record.