CVE-2023-53725: clocksource/drivers/cadence-ttc: Fix memory leak in ttc_timer_probe
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".
Security readout for executives and security teams
Plain-English summary
CVE-2023-53725 is a Linux kernel resource-cleanup flaw. The affected timer probe path may leak mapped memory and clock references during failure paths. The source bundle does not provide CVSS, CWE, confirmed impact, or active exploitation evidence.
Executive priority
Treat this as routine kernel maintenance unless affected embedded or custom Linux systems use this driver. There is no source-supported evidence of exploitation, but unmanaged kernel branches should still be corrected through normal patch cycles.
Technical view
The issue is in drivers/clocksource/timer-cadence-ttc.c ttc_timer_probe(). Smatch reported timer_baseaddr from of_iomap() was not released on several paths. The fix replaces it with devm_of_iomap() and adds clk_put() cleanup for clk_ce and clk_cs.
Likely exposure
Exposure appears limited to Linux kernels using the Cadence TTC clocksource driver path. The bundle lists Linux kernel version markers including 3.10, 4.19.291, 5.4.251, 5.10.188, 5.15.121, 6.1.39, 6.3.13, 6.4.4, and 6.5, but does not name distributions or devices.
Exploitation context
No active exploitation is supported by the provided sources. The CVE is not marked KEV, and the bundle describes a memory leak found by static analysis rather than an attacker workflow or public exploit.
Researcher notes
Evidence is limited to the CVE record and upstream stable commit references. The bundle lacks CVSS, CWE, affected distribution mapping, exploitability analysis, and detailed runtime impact. Avoid broad claims beyond the specific Linux kernel driver cleanup issue.
Mitigation direction
Apply kernel or distribution updates that include the referenced stable fixes.
For custom kernels, review and backport the vendor-approved cleanup patch.
Check vendor kernel advisories before assuming a branch is fixed.
Prioritize systems where the Cadence TTC driver is enabled or required.
Validation and detection
Inventory Linux kernel versions and downstream vendor package status.
Check whether the Cadence TTC clocksource driver is built or loaded.
Compare source trees against the referenced stable commits.
Review boot or probe logs for related driver initialization failures.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cve · low confidence lookup
CVE-2023-53725 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
0CVSS vectors
3Timeline events
0ADP providers
9Source links
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
CVE publishedCVE Program
The CVE record was published.
Oct 22, 2025, 13:23 UTC (UTC+00:00)
CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.