CVE-2023-54111: pinctrl: rockchip: Fix refcount leak in rockchip_pinctrl_parse_groups
In the Linux kernel, the following vulnerability has been resolved:
pinctrl: rockchip: Fix refcount leak in rockchip_pinctrl_parse_groups
of_find_node_by_phandle() 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.
Security readout for executives and security teams
Plain-English summary
This CVE covers a Linux kernel reference-count leak in the Rockchip pinctrl driver. The public record does not provide a CVSS score, CWE, or concrete attack impact. Treat it as a kernel maintenance issue for Rockchip-based systems, especially embedded or appliance fleets, and prioritize normal kernel updates through trusted vendor channels.
Executive priority
Low operational urgency unless you manage Rockchip-based appliances or embedded Linux fleets. No exploitation evidence is provided, but kernel refcount leaks should still be closed during routine patch cycles because embedded devices often lag behind upstream fixes.
Technical view
rockchip_pinctrl_parse_groups calls of_find_node_by_phandle, which increments a device-tree node reference count. The fix adds the missing of_node_put when the node is no longer needed. The source describes a refcount leak only; it does not establish privilege escalation, code execution, or a specific denial-of-service path.
Likely exposure
Exposure appears limited to Linux systems using affected kernel versions with the Rockchip pinctrl driver path. This is most relevant to Rockchip SoC devices, embedded Linux systems, and vendor kernels derived from the listed upstream stable ranges.
Exploitation context
The bundle marks KEV as false and provides no cited evidence of active exploitation or public exploit use. The described weakness is an internal kernel refcount leak during pinctrl group parsing, but the sources do not describe attacker control or trigger conditions.
Researcher notes
The record lacks CVSS, CWE, and exploitability analysis. Research should focus on whether untrusted device-tree data or repeated parsing paths can make the refcount leak security-relevant in real deployments. Avoid assuming impact beyond the source-described leak.
Mitigation direction
Update affected Linux kernels through distribution or device-vendor channels.
Confirm the vendor kernel includes the referenced upstream stable fix.
Prioritize Rockchip-based production devices and long-lived embedded images.
Monitor CVE and kernel stable guidance for revised severity or impact details.
Validation and detection
Inventory systems running Linux on Rockchip SoCs or vendor kernels.
Map deployed kernel versions against the affected version list.
Check kernel package changelogs for the referenced stable commits.
Confirm no unsupported custom kernel omits the of_node_put fix.
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-54111 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
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.
CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
CVE publishedCVE Program
The CVE record was published.
Dec 24, 2025, 13:06 UTC (UTC+00:00)
CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.