CVE-2022-50184: drm/meson: encoder_hdmi: Fix refcount leak in meson_encoder_hdmi_init
In the Linux kernel, the following vulnerability has been resolved:
drm/meson: encoder_hdmi: Fix refcount leak in meson_encoder_hdmi_init
of_graph_get_remote_node() returns remote device nodepointer with
refcount incremented, we should use of_node_put() on it when done.
Add missing of_node_put() to avoid refcount leak.
Security readout for executives and security teams
Plain-English summary
CVE-2022-50184 is a Linux kernel issue in the Meson HDMI display encoder code. The bug leaks a device-node reference during initialization, which can waste kernel resources. The public record does not provide CVSS, confirmed impact, or active exploitation evidence, so urgency depends on whether affected kernels and this hardware-specific driver are present.
Executive priority
Treat this as a routine kernel maintenance item unless your fleet includes exposed or business-critical systems using the affected Meson HDMI driver. There is no source-provided evidence of exploitation or severe impact, but unresolved kernel resource leaks should still be cleared through normal patch cycles.
Technical view
The resolved flaw is a missing of_node_put() after of_graph_get_remote_node() in meson_encoder_hdmi_init. Because the helper increments a device-node reference count, failing to release it causes a refcount leak. The affected component is Linux kernel drm/meson encoder_hdmi, with fixes referenced in stable kernel commits.
Likely exposure
Exposure is most likely on Linux systems running affected kernel versions where the drm/meson HDMI encoder path is built and used. The source bundle identifies Linux kernel versions and commits, but does not map them to specific distributions, devices, or package releases.
Exploitation context
The provided sources do not state active exploitation, public exploit availability, or KEV listing. The described weakness is a resource-management bug, so practical risk appears tied to local driver initialization behavior rather than a documented remote attack path.
Researcher notes
The evidence is narrow: a kernel fix description and stable commit references. No CVSS, CWE, exploit status, or distro-level advisory is included. Validate impact through kernel configuration, driver use, and whether downstream vendors backported the missing of_node_put() fix.
Mitigation direction
Apply Linux kernel updates that include the referenced stable fixes.
Check your distribution or device vendor advisory for backported kernel fixes.
Prioritize systems using the drm/meson HDMI encoder driver.
If upgrade timing is unclear, follow vendor guidance for temporary risk reduction.
Validation and detection
Inventory kernel versions against the affected versions in the CVE record.
Check whether the drm/meson HDMI encoder driver is built, loaded, or used.
Confirm your kernel includes one of the referenced stable fix commits or a backport.
Review vendor kernel changelogs for CVE-2022-50184 or the refcount leak fix.
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-50184 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.