# CVE-2023-53725: clocksource/drivers/cadence-ttc: Fix memory leak in ttc_timer_probe

> A memory leak in the Cadence TTC timer driver can lead to resource exhaustion and denial of service in the Linux kernel.

- **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:** 22 Oct 2025
- **Updated:** 11 May 2026
- **Also known as:** BELL-CVE-2023-53725, DEBIAN-CVE-2023-53725, GHSA-2gf7-3qxp-c9rr, UBUNTU-CVE-2023-53725

## What is CVE-2023-53725?

CVE-2023-53725 is a memory corruption vulnerability in Linux, published on 22 Oct 2025. 

### Official description

In the Linux kernel, the following vulnerability has been resolved:

clocksource/drivers/cadence-ttc: Fix memory leak in ttc_timer_probe

Smatch reports:
drivers/clocksource/timer-cadence-ttc.c:529 ttc_timer_probe()
warn: 'timer_baseaddr' from of_iomap() not released on lines: 498,508,516.

timer_baseaddr may have the problem of not being released after use,
I replaced it with the devm_of_iomap() function and added the clk_put()
function to cleanup the "clk_ce" and "clk_cs".

## Which versions are affected by CVE-2023-53725?


## How do I fix CVE-2023-53725?

Apply the vendor's patch.

## Is CVE-2023-53725 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-53725 and fix it if it is affected.

What it is: CVE-2023-53725 is a memory corruption vulnerability in Linux, published on 22 Oct 2025. 
Exploitation: There is no known exploitation of CVE-2023-53725 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-2023-53725/ (Markdown: https://insights.sbomify.com/CVE-2023-53725/index.md)
```

## Sources

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

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