LiveActive security incident?Get immediate response
CVE Record

CVE-2023-53818: ARM: zynq: Fix refcount leak in zynq_early_slcr_init

In the Linux kernel, the following vulnerability has been resolved: ARM: zynq: Fix refcount leak in zynq_early_slcr_init of_find_compatible_node() returns a node pointer with refcount incremented, we should use of_node_put() on error path. Add missing of_node_put() to avoid refcount leak.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

This CVE describes a Linux kernel cleanup bug in ARM Zynq startup code. An internal device-tree reference is not released on an error path, which can leak a kernel reference. The sources do not describe code execution, data exposure, privilege escalation, denial of service impact, or active exploitation.

Executive priority

Treat as a targeted kernel maintenance item, not an emergency, based on current evidence. The main business risk is unmanaged embedded Linux exposure where kernel patching is slow or opaque.

Technical view

In zynq_early_slcr_init, of_find_compatible_node() increments a device-tree node reference count. The fix adds the missing of_node_put() on an error path. Public metadata lists Linux kernel affected versions and stable-tree fixes, but provides no CVSS score, CWE, or impact analysis.

Likely exposure

Exposure appears limited to Linux systems using ARM Zynq kernel platform code within the affected kernel version set. Generic Linux servers without that platform path are less likely to be practically exposed, but the source bundle does not provide configuration-level reachability details.

Exploitation context

CISA KEV status is false in the provided bundle, and no cited source states active exploitation. The available evidence describes a refcount leak fix, not a public exploit path or weaponized technique.

Researcher notes

The record is sparse: no CVSS, CWE, exploit status, or impact details are provided. Analysis should focus on affected branch mapping, platform reachability, and whether downstream vendors backported the missing of_node_put() fix.

Mitigation direction

  • Review vendor or distribution kernel advisories for CVE-2023-53818 applicability.
  • Update affected Linux kernels to a version containing the referenced stable commits.
  • Prioritize embedded ARM Zynq fleets if they run listed affected kernel branches.
  • Track this through normal kernel maintenance unless vendor guidance raises impact.

Validation and detection

  • Inventory Linux kernel versions across ARM Zynq devices.
  • Check whether deployed kernels include one of the referenced stable fixes.
  • Confirm vendor BSP or distribution release notes mention this CVE or commit.
  • Document systems where Zynq platform code is not present or not reachable.
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-53818 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
LinuxLinux3329659df0300d1d0aa22f5e7063f83a88ef92aa, 3329659df0300d1d0aa22f5e7063f83a88ef92aa, 3329659df0300d1d0aa22f5e7063f83a88ef92aa, 3329659df0300d1d0aa22f5e7063f83a88ef92aa, 3329659df0300d1d0aa22f5e7063f83a88ef92aa, 3329659df0300d1d0aa22f5e7063f83a88ef92aa, 3329659df0300d1d0aa22f5e7063f83a88ef92aa, 3329659df0300d1d0aa22f5e7063f83a88ef92aaunaffected
LinuxLinux4.0, 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.