LiveActive security incident?Get immediate response
CVE Record

CVE-2023-53724: mfd: pcf50633-adc: Fix potential memleak in pcf50633_adc_async_read()

In the Linux kernel, the following vulnerability has been resolved: mfd: pcf50633-adc: Fix potential memleak in pcf50633_adc_async_read() `req` is allocated in pcf50633_adc_async_read(), but adc_enqueue_request() could fail to insert the `req` into queue. We need to check the return value and free it in the case of failure.

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

Security readout for executives and security teams

Plain-English summary

This is a Linux kernel memory leak in the PCF50633 ADC driver. If a request cannot be queued, allocated memory may not be freed. The sources do not provide CVSS, exploitability, or business-impact evidence, so urgency depends on whether affected kernels and this driver are present.

Executive priority

Treat as a targeted kernel hygiene issue, not an emergency based on current evidence. Prioritize systems with affected kernels and relevant hardware support during normal patch cycles.

Technical view

pcf50633_adc_async_read() allocates req, then calls adc_enqueue_request(). The vulnerable path failed to check enqueue failure and free req, creating a potential kernel memory leak. Stable kernel commits add failure handling and cleanup.

Likely exposure

Likely limited to Linux systems running affected kernel builds with the PCF50633 ADC driver code enabled or present. The bundle lists affected Linux versions but provides no CPEs or deployment context.

Exploitation context

The record is not in KEV, and the provided sources do not state active exploitation, exploit availability, remote attack surface, or required privileges.

Researcher notes

Evidence is narrow: the public record identifies a memory leak fix and stable commits, but not CVSS, CWE, exploit path, or attacker model. Avoid assuming remote exploitability without additional vendor analysis.

Mitigation direction

  • Check vendor kernel advisories for packages containing the referenced stable fixes.
  • Upgrade affected Linux kernels through the normal distribution or device vendor channel.
  • Prioritize embedded or legacy systems likely to include PCF50633 hardware support.
  • If no vendor package exists, track upstream stable commits for backport guidance.

Validation and detection

  • Inventory kernel versions against the CVE record and vendor advisory status.
  • Check whether PCF50633 ADC driver code is built, loaded, or packaged.
  • Confirm installed kernel changelogs include the referenced stable fix commits.
  • Monitor kernel memory behavior if vulnerable systems cannot be immediately updated.
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-53724 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
LinuxLinux08c3e06a5eb27d43b712adef18379f8464425e71, 08c3e06a5eb27d43b712adef18379f8464425e71, 08c3e06a5eb27d43b712adef18379f8464425e71, 08c3e06a5eb27d43b712adef18379f8464425e71, 08c3e06a5eb27d43b712adef18379f8464425e71, 08c3e06a5eb27d43b712adef18379f8464425e71, 08c3e06a5eb27d43b712adef18379f8464425e71, 08c3e06a5eb27d43b712adef18379f8464425e71unaffected
LinuxLinux2.6.29, 0, 4.14.308, 4.19.276, 5.4.235, 5.10.173, 5.15.99, 6.1.16, 6.2.3, 6.3affected
Weakness

CWE details

No CWE listed

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