LiveActive security incident?Get immediate response
CVE Record

CVE-2023-53610: irqchip: Fix refcount leak in platform_irqchip_probe

In the Linux kernel, the following vulnerability has been resolved: irqchip: Fix refcount leak in platform_irqchip_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 Linux kernel issue is a reference-count leak in irqchip probing. It means the kernel may fail to release an internal device-tree node reference after use. The provided sources do not show code execution, privilege escalation, data theft, CVSS scoring, or active exploitation.

Executive priority

Treat this as routine kernel hygiene unless vendor guidance raises severity for your environment. There is no source-backed evidence of exploitation or severe impact in the provided bundle.

Technical view

platform_irqchip_probe calls of_irq_find_parent(), which returns a node pointer with an incremented reference count. The fix adds of_node_put() when the node is no longer needed, preventing a reference-count leak in the Linux kernel irqchip path.

Likely exposure

Exposure is limited to Linux kernels that include the affected irqchip code path and the affected versions listed in the CVE bundle. The bundle does not provide distribution package mappings, architecture scope, or a complete affected range interpretation.

Exploitation context

CISA KEV status is false in the source bundle, and no cited source reports active exploitation. The provided material describes a resource-management bug, not an exploit technique or attacker workflow.

Researcher notes

The core evidence is a missing of_node_put() after of_irq_find_parent(). Impact is not quantified by CVSS or CWE data in the bundle. Validate affectedness through kernel source lineage or vendor backport status rather than version strings alone.

Mitigation direction

  • Check Linux vendor advisories for your distribution or appliance kernel.
  • Prioritize stable kernel updates containing the referenced upstream fixes.
  • Map running kernel versions against vendor package advisories.
  • For appliances, request firmware guidance from the vendor.

Validation and detection

  • Inventory Linux kernel versions across servers, appliances, and embedded systems.
  • Confirm whether vendor kernels include the referenced fix commits.
  • Review kernel update status in vulnerability management tooling.
  • Track exceptions where kernel upgrades require maintenance windows.
Prepared
Confidence
medium
Sources
7

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-53610 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
6Source 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
LinuxLinuxf8410e626569324cfe831aaecc0504cafc12b471, f8410e626569324cfe831aaecc0504cafc12b471, f8410e626569324cfe831aaecc0504cafc12b471, f8410e626569324cfe831aaecc0504cafc12b471, f8410e626569324cfe831aaecc0504cafc12b471unaffected
LinuxLinux5.9, 0, 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.