CVE-2022-50154: PCI: mediatek-gen3: Fix refcount leak in mtk_pcie_init_irq_domains()
In the Linux kernel, the following vulnerability has been resolved:
PCI: mediatek-gen3: Fix refcount leak in mtk_pcie_init_irq_domains()
of_get_child_by_name() returns a node pointer with refcount incremented, so
we should use of_node_put() on it when we don't need it anymore.
Add missing of_node_put() to avoid refcount leak.
Security readout for executives and security teams
Plain-English summary
CVE-2022-50154 is a Linux kernel resource-management bug in the MediaTek Gen3 PCIe driver. The driver failed to release a device-tree node reference after use, causing a reference-count leak. Based on the supplied sources, this is not described as remotely exploitable and is not listed in KEV.
Executive priority
Treat as routine patch-cycle work unless MediaTek-based Linux appliances are business-critical or stability-sensitive. There is no supplied evidence of active exploitation, but kernel fixes should still be tracked because embedded assets often patch slowly.
Technical view
The issue is in mtk_pcie_init_irq_domains(). of_get_child_by_name() increments the node reference count, but the affected code did not call of_node_put() when finished. The kernel fix adds the missing release to prevent a refcount leak in PCI interrupt-domain initialization for the mediatek-gen3 driver.
Likely exposure
Exposure is most likely on Linux systems using MediaTek Gen3 PCIe hardware or kernels that include the affected driver and affected version ranges. Generic servers and cloud workloads are less likely exposed unless they run this platform-specific kernel code. Exact distribution impact requires vendor mapping.
Exploitation context
The provided sources do not report active exploitation, public exploit use, or KEV listing. The evidence describes a reference-count leak, not a privilege escalation or remote code execution path. Business risk is mainly operational stability on affected MediaTek-based systems.
Researcher notes
Focus validation on platform reachability and kernel lineage. The key technical indicator is whether the kernel tree includes the stable commits fixing the missing of_node_put() in mtk_pcie_init_irq_domains(). Source evidence does not provide CVSS, CWE, exploitability, or distribution-specific fixed versions.
Mitigation direction
Update affected Linux kernels to versions containing the referenced stable fixes.
Check distribution or device-vendor advisories for backported fixes.
Prioritize MediaTek-based embedded, router, appliance, or ARM platforms.
Track kernel package updates through normal patch management.
Avoid inventing compensating controls without vendor confirmation.
Validation and detection
Inventory Linux kernel versions across MediaTek-based assets.
Confirm whether the mediatek-gen3 PCIe driver is present or enabled.
Check vendor kernel changelogs for the referenced stable commits.
Verify patched source includes the missing of_node_put() fix.
Run standard regression testing after kernel updates.
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-50154 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:03 UTC (UTC+00:00)
CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.