CVE-2022-50061: pinctrl: nomadik: Fix refcount leak in nmk_pinctrl_dt_subnode_to_map
In the Linux kernel, the following vulnerability has been resolved:
pinctrl: nomadik: Fix refcount leak in nmk_pinctrl_dt_subnode_to_map
of_parse_phandle() returns a node pointer with refcount
incremented, we should use of_node_put() on it when not need anymore.
Add missing of_node_put() to avoid refcount leak."
Security readout for executives and security teams
Plain-English summary
This CVE describes a Linux kernel reference-count leak in the Nomadik pinctrl driver. In practical terms, a kernel object reference is not released after parsing a device-tree phandle. The public record does not provide CVSS, confirmed impact, or active exploitation evidence, so urgency should be driven by affected-kernel inventory and vendor kernel advisories.
Executive priority
Handle through normal kernel maintenance unless asset inventory shows affected embedded or specialized Linux platforms. There is no source-backed evidence of active exploitation or critical severity, but unsupported kernels should be upgraded because vendor backport status is the real control point.
Technical view
The issue is in nmk_pinctrl_dt_subnode_to_map. of_parse_phandle() returns a device-tree node with an incremented refcount, but the vulnerable code did not call of_node_put() when finished. Kernel stable commits add the missing release to avoid the refcount leak.
Likely exposure
Exposure appears limited to Linux kernels containing the Nomadik pinctrl code in the affected ranges listed by the CVE record. Real-world exposure depends on kernel configuration, device-tree use, hardware platform, and distribution backports. The source bundle does not identify affected distributions or cloud images.
Exploitation context
The source bundle does not cite exploitation, proof-of-concept code, KEV listing, or attacker prerequisites. It only documents a resolved kernel refcount leak. Treat active exploitation as unproven unless a vendor or authoritative source later states otherwise.
Researcher notes
The public details support a memory-management correctness issue rather than a fully characterized exploit path. Key unanswered items are practical triggerability, privilege boundary impact, and distribution backport mapping. Do not infer exploitability beyond the documented missing of_node_put() fix.
Mitigation direction
Check distribution kernel advisories for CVE-2022-50061 coverage.
Update to a vendor kernel containing the referenced stable fix.
Prioritize systems using affected Linux kernels and Nomadik pinctrl support.
If patching is delayed, document vendor-supported compensating guidance only.
Avoid assuming generic server exposure without kernel configuration evidence.
Validation and detection
Inventory running kernel versions and vendor package build metadata.
Check whether the kernel includes the Nomadik pinctrl driver.
Compare vendor changelogs against the referenced stable commits.
Confirm CVE-2022-50061 is fixed through package advisory data.
Record any unsupported or end-of-life kernels for upgrade planning.
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-2022-50061 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.
Jun 18, 2025, 11:02 UTC (UTC+00:00)
CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.