CVE-2022-50161: mtd: maps: Fix refcount leak in of_flash_probe_versatile
In the Linux kernel, the following vulnerability has been resolved:
mtd: maps: Fix refcount leak in of_flash_probe_versatile
of_find_matching_node_and_match() 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
CVE-2022-50161 is a Linux kernel resource-management bug in MTD flash map probing. The code increments a device-tree node reference and fails to release it. The public data does not provide CVSS, impact severity, or exploitation evidence, so urgency depends on whether affected kernels and this hardware path are present.
Executive priority
Track and remediate through normal kernel maintenance unless asset inventory shows exposed embedded systems or vendor advisories raise severity. There is no supplied evidence supporting emergency response.
Technical view
The resolved issue is a missing of_node_put() after of_find_matching_node_and_match() in of_flash_probe_versatile. That causes a device-tree node refcount leak. The source bundle lists Linux kernel versions and stable commits addressing the issue, but does not describe privilege requirements, attack vectors, or practical impact.
Likely exposure
Exposure appears limited to Linux systems running affected kernel versions where the mtd maps of_flash_probe_versatile code path is used. This is more likely relevant to embedded or hardware-specific Linux deployments than general userland software.
Exploitation context
The bundle marks KEV as false and provides no cited evidence of active exploitation, public exploitability, or weaponized abuse. Treat exploitation status as unproven based on the supplied sources.
Researcher notes
Evidence is sparse: no CVSS, CWE, exploit status, or detailed impact is provided. Analysis should stay tied to the kernel commit description: a missing of_node_put() causing a refcount leak in a specific MTD map probe path.
Mitigation direction
Identify Linux kernel versions across managed assets.
Check whether affected systems use MTD maps or relevant device-tree flash probing.
Apply vendor or kernel stable updates containing the referenced fixes.
Prioritize embedded and appliance-like Linux deployments for review.
Monitor Linux distributor advisories for packaged kernel guidance.
Validation and detection
Compare running kernel versions against the affected versions in the CVE record.
Review vendor kernel changelogs for the referenced stable commits.
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-50161 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:03 UTC (UTC+00:00)
CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.