LiveActive security incident?Get immediate response
CVE Record

CVE-2023-53687: tty: serial: samsung_tty: Fix a memory leak in s3c24xx_serial_getclk() when iterating clk

In the Linux kernel, the following vulnerability has been resolved: tty: serial: samsung_tty: Fix a memory leak in s3c24xx_serial_getclk() when iterating clk When the best clk is searched, we iterate over all possible clk. If we find a better match, the previous one, if any, needs to be freed. If a better match has already been found, we still need to free the new one, otherwise it leaks.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysislow

Security readout for executives and security teams

Plain-English summary

CVE-2023-53687 is a Linux kernel memory leak in the Samsung serial TTY driver clock-selection logic. The public record does not provide CVSS, impact metrics, or evidence of active exploitation. Treat it as a kernel maintenance issue unless your fleet uses affected Samsung S3C24xx serial driver paths.

Executive priority

Low urgency for most enterprise fleets, higher only for managed devices using affected Samsung serial driver paths. Track through normal kernel patch cycles unless vendor guidance raises impact.

Technical view

The flaw is in s3c24xx_serial_getclk() in samsung_tty. While iterating candidate clocks, the code could fail to release previously or newly referenced clocks when a better match was found, causing a memory leak. Linux stable commits are cited as the resolution evidence.

Likely exposure

Exposure is most likely on Linux systems whose kernels include and use the Samsung S3C24xx serial TTY driver. General-purpose Linux servers without this driver path are less likely to be exposed, but kernel configuration and vendor backports must be checked.

Exploitation context

The source bundle shows no KEV listing, no CVSS score, and no cited public exploitation evidence. The issue is described as a memory leak, not code execution or privilege escalation. Evidence is incomplete for real-world exploitability.

Researcher notes

The record lacks CVSS, CWE, and exploitation details. Analysis should stay limited to the described memory leak and the kernel stable fixes. Avoid assuming denial-of-service impact without reproducer or vendor impact statement.

Mitigation direction

  • Check the Linux vendor or distribution advisory for your exact kernel build.
  • Update to a kernel containing the referenced stable fix for your supported branch.
  • For vendor kernels, confirm whether the fix was backported rather than relying on version strings.
  • Prioritize embedded or ARM systems using Samsung S3C24xx serial hardware paths.

Validation and detection

  • Inventory Linux kernel versions and vendor kernel branches in affected device classes.
  • Confirm whether the samsung_tty S3C24xx driver is built or loaded.
  • Compare your kernel source or changelog against the referenced stable commits.
  • Review vendor advisories for fixed package versions and backport status.
Prepared
Confidence
medium
Sources
10

Public sources used

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-53687 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

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.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux5f5a7a5578c5885201cf9c85856f023fe8b81765, 5f5a7a5578c5885201cf9c85856f023fe8b81765, 5f5a7a5578c5885201cf9c85856f023fe8b81765, 5f5a7a5578c5885201cf9c85856f023fe8b81765, 5f5a7a5578c5885201cf9c85856f023fe8b81765, 5f5a7a5578c5885201cf9c85856f023fe8b81765, 5f5a7a5578c5885201cf9c85856f023fe8b81765, 5f5a7a5578c5885201cf9c85856f023fe8b81765unaffected
LinuxLinux3.3, 0, 4.14.322, 4.19.291, 5.4.251, 5.10.188, 5.15.121, 6.1.40, 6.4.5, 6.5affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.