Service interruption via EMC error-path memory leak
Published Oct 1, 2025 · Updated Oct 1, 2025
Memory leakage in the Tegra124 EMC clock driver in Linux 4.2 through 6.4.3 allows local users to interrupt service during initialization. The load_timings_from_dt error path fails to free its allocated timing table, and tegra_clk_register_emc also returns without freeing the Tegra EMC object. The condition requires a Tegra124 system to encounter a timing-load failure during EMC clock setup; repeated failures can exhaust kernel memory and interrupt service.
Summary
What happened
Memory leakage in the Tegra124 EMC clock driver in Linux 4.2 through 6.4.3 allows local users to interrupt service during initialization. The load_timings_from_dt error path fails to free its allocated timing table, and tegra_clk_register_emc also returns without freeing the Tegra EMC object. The condition requires a Tegra124 system to encounter a timing-load failure during EMC clock setup; repeated failures can exhaust kernel memory and interrupt service.
The record
- CVE
- CVE-2023-53505
- Published
- Oct 1, 2025
- Updated
- Oct 1, 2025
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-401, T1499.001
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Oct 1, 2025CVE publishedPublication date reported by the CVE source.
- Oct 1, 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=2db04f16b589c6c96bd07df3f1ef8558bfdb6810 <404e9f741acfb188212f7142d91e247630dd77cc
- Affected versionversion=2db04f16b589c6c96bd07df3f1ef8558bfdb6810 <4e59e355f9fcccd9edf65d09f769bb4c163a1c36
- Affected versionversion=2db04f16b589c6c96bd07df3f1ef8558bfdb6810 <53a06e5924c0d43c11379a08c5a78529c3e61595
- Affected versionversion=2db04f16b589c6c96bd07df3f1ef8558bfdb6810 <801c8341f7aff07c494b53e627970b72635af5d3
- Affected versionversion=2db04f16b589c6c96bd07df3f1ef8558bfdb6810 <96bafece6ff380138896f009141fd7337070e680
- Affected versionversion=2db04f16b589c6c96bd07df3f1ef8558bfdb6810 <e969c144d908ea9387442659f103d374c8ff682d
- Affected versionversion=2db04f16b589c6c96bd07df3f1ef8558bfdb6810 <fd1c117bb5d7e033bf1aa25ac97ff421f81a1199
- Affected versionversion=4.2
What conditions does exploitation require?
What is affected?
Published CVSS scores
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
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