Kernel memory leak via unreleased clock reference
Published Dec 9, 2025 · Updated May 11, 2026
Memory leak in the samsung_tty serial driver in Linux 3.3 and later allows attackers to leak kernel memory via failed clock-rate lookups. On the error path in s3c24xx_serial_getclk(), clk_get_rate() failure returns without releasing the newly acquired clk reference. The public record does not identify an attacker-controlled trigger or establish that repeated failures interrupt service.
Summary
What happened
Memory leak in the samsung_tty serial driver in Linux 3.3 and later allows attackers to leak kernel memory via failed clock-rate lookups. On the error path in s3c24xx_serial_getclk(), clk_get_rate() failure returns without releasing the newly acquired clk reference. The public record does not identify an attacker-controlled trigger or establish that repeated failures interrupt service.
The record
- CVE
- CVE-2023-53858
- Published
- Dec 9, 2025
- Updated
- May 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- Unavailable
- Attack vector
- Unavailable
- Privileges
- Unavailable
Timeline
How it unfolded
- Dec 9, 2025CVE publishedPublication date reported by the CVE source.
- May 11, 2026Record 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.3
- Affected versionversion=5f5a7a5578c5885201cf9c85856f023fe8b81765 <073dbbe5743779faf24f233cc95459b47c7198dd
- Affected versionversion=5f5a7a5578c5885201cf9c85856f023fe8b81765 <1694fc8ad734e2909a9e40d2be03cc4423e0bee6
- Affected versionversion=5f5a7a5578c5885201cf9c85856f023fe8b81765 <30962268fa1a7466413b3d83037688129021d470
- Affected versionversion=5f5a7a5578c5885201cf9c85856f023fe8b81765 <34f5b826dd509b76644f83094b4af7e7668a6a38
- Affected versionversion=5f5a7a5578c5885201cf9c85856f023fe8b81765 <755289d67eb9a74ae71bb624902e979c66859444
- Affected versionversion=5f5a7a5578c5885201cf9c85856f023fe8b81765 <a49e5a05121c8bc471a57b4916c5393749c24de5
- Affected versionversion=5f5a7a5578c5885201cf9c85856f023fe8b81765 <a9c09546e903f1068acfa38e1ee18bded7114b37
- Affected versionversion=5f5a7a5578c5885201cf9c85856f023fe8b81765 <f47e6631a8fcc6fe05b8644aa4222a60f3b0a927
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