CVE-2022-50120: remoteproc: imx_rproc: Fix refcount leak in imx_rproc_addr_init
In the Linux kernel, the following vulnerability has been resolved:
remoteproc: imx_rproc: Fix refcount leak in imx_rproc_addr_init
of_parse_phandle() returns a node pointer with refcount
incremented, we should use of_node_put() on it when not needed anymore.
This function has two paths missing of_node_put().
Security readout for executives and security teams
Plain-English summary
This CVE is a Linux kernel resource-management bug in the i.MX remote processor driver. The public record describes a missing reference release, not a confirmed remote compromise path. Business urgency depends on whether your devices run affected Linux kernels with this driver in use.
Executive priority
Handle as routine kernel maintenance unless your environment relies heavily on i.MX remote processor functionality. Escalate only if vendor guidance later confirms meaningful denial-of-service or security impact.
Technical view
The issue is in remoteproc imx_rproc_addr_init. of_parse_phandle() increments a device-tree node reference count, and two error or exit paths failed to call of_node_put(), causing a refcount leak. Kernel stable commits are referenced as the resolution.
Likely exposure
Likely limited to Linux systems whose kernel includes and uses the imx_rproc remoteproc driver, typically i.MX-based embedded or edge devices. The source bundle does not identify specific distributions, appliances, or cloud platforms.
Exploitation context
The supplied sources do not report active exploitation, public exploit availability, KEV listing, CVSS score, or a demonstrated privilege impact. Treat exploitability as unproven from the provided evidence.
Researcher notes
Evidence is narrow: the CVE text describes a missing of_node_put() after of_parse_phandle(). No CVSS, CWE, exploit status, or operational impact is provided. Analysis should avoid assuming remote reachability or privilege escalation.
Mitigation direction
Check Linux distribution or device vendor guidance for CVE-2022-50120.
Update to a kernel containing the referenced stable commits when available.
Prioritize i.MX-based devices using remoteproc or imx_rproc support.
Track vendor advisories if kernels are maintained by an OEM or BSP provider.
Validation and detection
Inventory Linux kernel versions across embedded and edge fleets.
Confirm whether imx_rproc support is built, loaded, or used.
Compare kernel source or package changelogs against referenced stable commits.
Document systems where vendor fix status remains unknown.
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-50120 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
5Source 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.