CVE-2022-50158: mtd: partitions: Fix refcount leak in parse_redboot_of
In the Linux kernel, the following vulnerability has been resolved:
mtd: partitions: Fix refcount leak in parse_redboot_of
of_get_child_by_name() 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-50158 is a Linux kernel memory/reference management defect in RedBoot MTD partition parsing. The source describes a missing reference release that can leak a device-tree node reference. No CVSS score, CWE, or business-impact detail is provided, so urgency should be driven by kernel exposure and vendor guidance.
Executive priority
Handle through normal kernel patch governance unless vendor guidance raises severity. There is no provided evidence of active exploitation or high-impact behavior, but affected kernels should still be remediated because kernel defects can accumulate operational risk.
Technical view
The Linux kernel fix adds a missing of_node_put() after of_get_child_by_name() in parse_redboot_of. The cited issue is a refcount leak in MTD partition handling. The record lists affected Linux kernel versions and stable commit references, but does not describe privilege requirements, crashability, or confidentiality/integrity impact.
Likely exposure
Exposure appears limited to Linux kernels in the listed affected version ranges where the RedBoot MTD partition parsing path is present or reachable. The bundle does not identify specific distributions, appliances, cloud images, or configurations that are confirmed affected.
Exploitation context
The bundle provides no evidence of active exploitation, and KEV is false. It also provides no proof-of-concept status or exploitability analysis. Treat this as a kernel maintenance vulnerability unless vendor advisories identify a stronger operational impact.
Researcher notes
The available evidence supports a narrow refcount leak finding, not a broader exploit narrative. Key missing details include reachable configurations, practical impact, trigger conditions, privilege context, and fixed release mapping beyond upstream stable commit references.
Mitigation direction
Update to a kernel containing the referenced stable fix commits.
Use vendor or distribution advisories to map fixed package versions.
Prioritize systems using MTD or RedBoot partition handling.
If patching is delayed, document affected kernel inventory and compensating controls.
Do not infer unsupported workarounds from the CVE text alone.
Validation and detection
Inventory Linux kernel versions across managed assets.
Check whether deployed kernels include the referenced stable commits.
Review vendor advisories for affected distribution package mappings.
Assess whether systems use MTD RedBoot partition parsing.
Track remediation evidence in vulnerability management records.
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-50158 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
7Source 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.