LiveActive security incident?Get immediate response
CVE Record

CVE-2023-53858: tty: serial: samsung_tty: Fix a memory leak in s3c24xx_serial_getclk() in case of error

In the Linux kernel, the following vulnerability has been resolved: tty: serial: samsung_tty: Fix a memory leak in s3c24xx_serial_getclk() in case of error If clk_get_rate() fails, the clk that has just been allocated needs to be freed.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

CVE-2023-53858 is a Linux kernel memory leak in the Samsung TTY serial driver error path. If a clock-rate lookup fails, an allocated clock reference was not released. The public record does not provide CVSS severity, business impact detail, or evidence of exploitation.

Executive priority

Handle through normal kernel patch management, with higher attention for embedded Linux products and appliances. Current evidence does not justify emergency response, but unresolved kernel memory leaks can affect reliability and should not remain indefinitely.

Technical view

The issue is in s3c24xx_serial_getclk() in drivers/tty/serial/samsung_tty. The fix releases the just-acquired clk object when clk_get_rate() fails. Source data identifies Linux kernel version records as affected and links multiple stable-branch commits carrying the correction.

Likely exposure

Exposure is most likely on Linux systems using kernels that include the vulnerable Samsung TTY serial driver code, especially embedded or ARM/Samsung platform builds. The source bundle does not confirm exploitability from remote, local, or unprivileged contexts.

Exploitation context

No active exploitation is supported by the provided sources. KEV is false, and the bundle contains no public exploit report, proof-of-concept reference, or attacker workflow. Treat this as a kernel maintenance vulnerability unless vendor guidance says otherwise.

Researcher notes

The record describes a narrow cleanup bug: clk reference allocation is not freed after clk_get_rate() failure. Missing data includes CVSS, CWE, reachable trigger conditions, privilege requirements, and impact beyond memory leak. Avoid assuming denial of service without validation.

Mitigation direction

  • Identify systems running Linux kernels with the Samsung TTY serial driver enabled.
  • Apply the relevant upstream or distribution kernel update containing the linked stable fixes.
  • Check Linux distribution advisories for packaged kernel backports and release timing.
  • Prioritize embedded or appliance fleets that use Samsung serial hardware support.

Validation and detection

  • Inventory kernel versions across affected Linux systems.
  • Check whether samsung_tty support is built in or loaded as a module.
  • Confirm the relevant stable fix commit or vendor backport is present.
  • Review kernel update status from the operating system vendor.
Prepared
Confidence
medium
Sources
10

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-53858 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.

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.