LiveActive security incident?Get immediate response
CVE Record

CVE-2023-53592: gpio: sifive: Fix refcount leak in sifive_gpio_probe

In the Linux kernel, the following vulnerability has been resolved: gpio: sifive: Fix refcount leak in sifive_gpio_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
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

This is a Linux kernel resource-management bug in the SiFive GPIO driver. A missing reference release can leak a kernel device-tree node reference during driver probing. The sources do not provide CVSS, confirmed exploitation, or broad impact details.

Executive priority

Track as a routine kernel maintenance item unless your environment includes affected SiFive/RISC-V platforms. There is no source-backed evidence of active exploitation or high business impact in the provided bundle.

Technical view

In sifive_gpio_probe, of_irq_find_parent() returns a node pointer with an incremented reference count. The kernel fix adds of_node_put() after use to prevent a reference-count leak. Evidence is limited to the CVE record and Linux stable commits.

Likely exposure

Likely limited to Linux systems using the SiFive GPIO driver on relevant SiFive or RISC-V device-tree hardware. Generic exposure depends on kernel version, distro backports, build configuration, and whether the driver is present and used.

Exploitation context

The source bundle states KEV is false and provides no cited evidence of active exploitation, public exploit activity, or practical attack requirements. Treat exploitation status as unconfirmed, not actively exploited.

Researcher notes

The record describes a refcount leak, not memory corruption or privilege escalation. Key gaps are missing CVSS, CWE, exploitability analysis, and precise affected-version ranges beyond the CVE version data and stable commit references.

Mitigation direction

  • Check your Linux distribution or vendor advisory for fixed kernel packages.
  • Upgrade to a kernel containing the referenced stable fixes when available.
  • Prioritize affected SiFive/RISC-V systems using this GPIO driver.
  • If no vendor package exists, assess applying the upstream stable patch.

Validation and detection

  • Inventory kernel versions on relevant Linux assets.
  • Confirm whether the SiFive GPIO driver is built, loaded, or used.
  • Check distro changelogs for the referenced stable commit IDs.
  • Review kernel logs for repeated driver probe failures or resource warnings.
Prepared
Confidence
medium
Sources
7

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

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux96868dce644d002383f6d5eb575a6ce3c8779f39, 96868dce644d002383f6d5eb575a6ce3c8779f39, 96868dce644d002383f6d5eb575a6ce3c8779f39, 96868dce644d002383f6d5eb575a6ce3c8779f39, 96868dce644d002383f6d5eb575a6ce3c8779f39unaffected
LinuxLinux5.6, 0, 5.10.163, 5.15.87, 6.0.19, 6.1.5, 6.2affected
Weakness

CWE details

No CWE listed

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