Local denial of service via leaked clock references
Published Oct 7, 2025 · Updated Oct 7, 2025
Memory leak in the Linux kernel Samsung serial driver allows local users to interrupt service by exhausting kernel memory. When s3c24xx_serial_getclk() searches candidate clocks, it retains superseded and rejected clock references instead of releasing them with clk_put(). The path requires local low-privileged access and a system using the Samsung serial driver; repeated clock selection exhausts kernel memory and interrupts service.
Summary
What happened
Memory leak in the Linux kernel Samsung serial driver allows local users to interrupt service by exhausting kernel memory. When s3c24xx_serial_getclk() searches candidate clocks, it retains superseded and rejected clock references instead of releasing them with clk_put(). The path requires local low-privileged access and a system using the Samsung serial driver; repeated clock selection exhausts kernel memory and interrupts service.
The record
- CVE
- CVE-2023-53687
- Published
- Oct 7, 2025
- Updated
- Oct 7, 2025
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-401, T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Oct 7, 2025CVE publishedPublication date reported by the CVE source.
- Oct 7, 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.3
- Affected versionversion=5f5a7a5578c5885201cf9c85856f023fe8b81765 <01dd8a43a84616c830782166ba3cceb01ad95363
- Affected versionversion=5f5a7a5578c5885201cf9c85856f023fe8b81765 <1962717c4649e026a4252fe6625175affd28a593
- Affected versionversion=5f5a7a5578c5885201cf9c85856f023fe8b81765 <1f426293fef1c13742b2a685bf7e363f51f6ee03
- Affected versionversion=5f5a7a5578c5885201cf9c85856f023fe8b81765 <46574e5a0a2aee41e6ebb979cfe1dbaea8693e16
- Affected versionversion=5f5a7a5578c5885201cf9c85856f023fe8b81765 <832e231cff476102e8204a9e7bddfe5c6154a375
- Affected versionversion=5f5a7a5578c5885201cf9c85856f023fe8b81765 <933e5b2998bc3a527d15efbf1e97c9e63297aa3c
- Affected versionversion=5f5a7a5578c5885201cf9c85856f023fe8b81765 <9dd8091959bc41fee51d0827276a2b982e84adf0
- Affected versionversion=5f5a7a5578c5885201cf9c85856f023fe8b81765 <f0bf102ef9b05d7294bd8d506755465f6867d944
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