LiveActive security incident?Get immediate response
CVE Record

CVE-2023-54205: pinctrl: stm32: Fix refcount leak in stm32_pctrl_get_irq_domain

In the Linux kernel, the following vulnerability has been resolved: pinctrl: stm32: Fix refcount leak in stm32_pctrl_get_irq_domain 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 CVE is a Linux kernel resource-management bug in the STM32 pin-control driver. The available sources describe a reference-count leak, not a remote code execution issue. Business urgency depends on whether your environment uses STM32-based Linux systems or vendor kernels carrying the affected code.

Executive priority

Treat as a targeted embedded-Linux maintenance item, not an enterprise-wide emergency from the current evidence. Patch affected STM32 or custom-kernel products through normal vulnerability management, escalating only where reliability or safety requirements are high.

Technical view

stm32_pctrl_get_irq_domain calls of_irq_find_parent(), which returns a device-tree node with an incremented reference count. The fix adds the missing of_node_put() when the node is no longer needed. The public record does not provide CVSS, CWE, exploitability, or concrete security impact details.

Likely exposure

Likely limited to Linux systems using the STM32 pinctrl driver path, commonly embedded or device-oriented deployments. The CVE source lists Linux kernel affected entries including 5.2, 5.4.235, 5.10.173, 5.15.99, 6.1.16, 6.2.3, and 6.3.

Exploitation context

The provided bundle says KEV is false and includes no cited evidence of active exploitation or public weaponization. Based on the description, this is a reference leak in kernel driver logic; operational impact is not fully established in the sources.

Researcher notes

Evidence is sparse: no CVSS, CWE, exploit narrative, or impact analysis is provided. The confirmed issue is the missing of_node_put() after of_irq_find_parent(). Avoid broad claims beyond affected Linux/STM32 driver exposure unless additional vendor advisories support them.

Mitigation direction

  • Update to a kernel or vendor build that includes the referenced stable fixes.
  • Prioritize STM32-based embedded Linux assets and custom kernels for review.
  • Check distribution or device-vendor advisories for backported fixes.
  • Track kernel lifecycle status for affected 5.x and 6.x deployments.

Validation and detection

  • Inventory systems running Linux on STM32 or using the STM32 pinctrl driver.
  • Compare kernel source or vendor changelogs against the referenced stable commits.
  • Confirm deployed kernel versions against vendor-fixed package versions.
  • Review device-tree and kernel configuration evidence for STM32 pinctrl usage.
Prepared
Confidence
medium
Sources
8

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-54205 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
7Source 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
LinuxLinuxd86f4d71e42a9fa1866f030074e54d7571d16ec1, d86f4d71e42a9fa1866f030074e54d7571d16ec1, d86f4d71e42a9fa1866f030074e54d7571d16ec1, d86f4d71e42a9fa1866f030074e54d7571d16ec1, d86f4d71e42a9fa1866f030074e54d7571d16ec1, d86f4d71e42a9fa1866f030074e54d7571d16ec1unaffected
LinuxLinux5.2, 0, 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.