LiveActive security incident?Get immediate response
CVE Record

CVE-2023-53757: irqchip/irq-mvebu-gicp: Fix refcount leak in mvebu_gicp_probe

In the Linux kernel, the following vulnerability has been resolved: irqchip/irq-mvebu-gicp: Fix refcount leak in mvebu_gicp_probe of_irq_find_parent() returns a node pointer with refcount incremented, We should use of_node_put() on it when not needed anymore. Add missing of_node_put() to avoid refcount leak.

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 resource-management bug in the irq-mvebu-gicp probe path. A reference counter is incremented and not released, creating a leak. The sources do not provide a CVSS score, concrete security impact, or evidence of active exploitation.

Executive priority

Treat as a routine kernel maintenance item unless vendor guidance identifies higher impact. There is no sourced evidence of active exploitation or broad emergency exposure, but affected kernels should still be updated through normal patch cycles.

Technical view

of_irq_find_parent() returns a device-tree node with an incremented reference count. mvebu_gicp_probe() failed to call of_node_put() when finished, causing a refcount leak. Stable kernel commits add the missing release. Impact is not quantified in the provided CVE data.

Likely exposure

Exposure is limited to Linux systems running affected kernel versions or commits that include the irq-mvebu-gicp code path. The bundle lists Linux as the affected product, but does not identify distributions, appliances, or cloud images.

Exploitation context

No active exploitation is supported by the supplied evidence. The CVE is not marked KEV, and the source bundle provides no public exploit, attack prerequisites, or demonstrated security outcome beyond the refcount leak.

Researcher notes

The evidence supports a narrow kernel refcount leak fix, not a confirmed privilege escalation, remote compromise, or denial-of-service scenario. Severity, CWE, and CVSS are absent, so exploitability and operational impact remain incomplete from the supplied sources.

Mitigation direction

  • Check vendor kernel advisories for your exact distribution or device.
  • Update to a kernel containing the referenced stable fix for your branch.
  • Prioritize systems using the irq-mvebu-gicp driver path.
  • Track this through normal kernel patch management unless vendor guidance says otherwise.

Validation and detection

  • Inventory Linux kernel versions across affected assets.
  • Compare running kernels against the affected versions and stable commit references.
  • Confirm vendor packages include the missing of_node_put() fix.
  • Review device-tree and kernel configuration for irq-mvebu-gicp usage.
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-53757 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
LinuxLinuxa68a63cb4dfc30e8a79b444aabc7747bb7621acf, a68a63cb4dfc30e8a79b444aabc7747bb7621acf, a68a63cb4dfc30e8a79b444aabc7747bb7621acf, a68a63cb4dfc30e8a79b444aabc7747bb7621acf, a68a63cb4dfc30e8a79b444aabc7747bb7621acf, a68a63cb4dfc30e8a79b444aabc7747bb7621acf, a68a63cb4dfc30e8a79b444aabc7747bb7621acf, a68a63cb4dfc30e8a79b444aabc7747bb7621acfunaffected
LinuxLinux4.13, 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.