Kernel resource leak via incomplete probe cleanup
Published Oct 22, 2025 · Updated Oct 22, 2025
Memory leak in the Cadence TTC clocksource driver in Linux allows attackers to cause unspecified impact via unspecified vectors. In ttc_timer_probe, three failure exits after of_iomap leave timer_baseaddr mapped, and clock references for clk_ce and clk_cs also lack cleanup. The condition is reached during Cadence TTC device probing; the published record does not identify an attacker-controlled trigger or a consequence beyond retained kernel resources.
Summary
What happened
Memory leak in the Cadence TTC clocksource driver in Linux allows attackers to cause unspecified impact via unspecified vectors. In ttc_timer_probe, three failure exits after of_iomap leave timer_baseaddr mapped, and clock references for clk_ce and clk_cs also lack cleanup. The condition is reached during Cadence TTC device probing; the published record does not identify an attacker-controlled trigger or a consequence beyond retained kernel resources.
The record
- CVE
- CVE-2023-53725
- Published
- Oct 22, 2025
- Updated
- Oct 22, 2025
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- Unavailable
- Attack vector
- Unavailable
- Privileges
- Unavailable
Timeline
How it unfolded
- Oct 22, 2025CVE publishedPublication date reported by the CVE source.
- Oct 22, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=3.10
- Affected versionversion=e932900a3279b5dbb6d8f43c7b369003620e137c <289e2054eeb63c9e133960731c342eeffad218d3
- Affected versionversion=e932900a3279b5dbb6d8f43c7b369003620e137c <54cc10a0f4b01b522e9519014200f1b33bf7e4aa
- Affected versionversion=e932900a3279b5dbb6d8f43c7b369003620e137c <67d7eebbc424935dec61fb352d1ccae5d16cf429
- Affected versionversion=e932900a3279b5dbb6d8f43c7b369003620e137c <8b5bf64c89c7100c921bd807ba39b2eb003061ab
- Affected versionversion=e932900a3279b5dbb6d8f43c7b369003620e137c <919dd531ebb7514f205ae7aab87994337ebce1f6
- Affected versionversion=e932900a3279b5dbb6d8f43c7b369003620e137c <99744200f28b2cf5f50767447e51b4b4a977d145
- Affected versionversion=e932900a3279b5dbb6d8f43c7b369003620e137c <e0a9cc90ea44a50d76a84f9f9bf1703d31fe45e9
- Affected versionversion=e932900a3279b5dbb6d8f43c7b369003620e137c <ebdff0986513a29be242aace0ef89b6c105b0bf0
What conditions does exploitation require?
What is affected?
Published CVSS scores
No CVSS assessment is available in this record.
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
No sourced classifications are available.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo