CVE-2022-50183: drm/meson: encoder_cvbs: Fix refcount leak in meson_encoder_cvbs_init
In the Linux kernel, the following vulnerability has been resolved:
drm/meson: encoder_cvbs: Fix refcount leak in meson_encoder_cvbs_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
This CVE is a Linux kernel resource-management bug in the Meson DRM CVBS encoder initialization path. A device-tree node reference was not released, causing a reference-count leak. The public record does not provide CVSS, CWE, exploit evidence, or impact beyond the leak, so business urgency should be driven by kernel exposure and vendor advisories.
Executive priority
Handle through normal kernel patch management unless vendor guidance raises severity. There is no supplied evidence of active exploitation or high-impact compromise, but kernel resource leaks can affect reliability and should not remain unmanaged on exposed or critical systems.
Technical view
The issue is in drm/meson encoder_cvbs initialization. of_graph_get_remote_node() increments a remote device node reference, but the vulnerable code failed to call of_node_put() when finished. The documented fix adds the missing release to prevent the leak. No source in the bundle describes privilege escalation, code execution, or a trigger path.
Likely exposure
Potential exposure is limited to Linux kernels containing the affected drm/meson CVBS encoder code path. The bundle lists Linux as affected, including versions around 5.17, 5.18.18, 5.19.2, and 6.0, but the version data is incomplete and should be verified against vendor kernel packages.
Exploitation context
The CVE is not listed as KEV in the supplied bundle, and no cited source reports active exploitation. The available evidence describes a refcount leak fix only. Treat exploitability and practical impact as unproven from these sources.
Researcher notes
The strongest evidence is the upstream kernel fix description and stable commit references. The public bundle lacks CVSS, CWE, exploit details, affected configuration specifics, and distribution package mappings. Avoid overstating impact until vendor advisories or kernel analysis establish reachability and consequence.
Mitigation direction
Check your Linux distribution or kernel vendor advisory for CVE-2022-50183 status.
Update to a kernel build containing the referenced stable fixes when available.
Prioritize systems using kernels with the drm/meson CVBS encoder path.
Track vendor backports, since fixed package versions may differ from upstream versions.
Validation and detection
Inventory deployed Linux kernel versions and vendor package release notes.
Confirm whether the kernel source includes the missing of_node_put() fix.
Check whether drm/meson CVBS encoder support is built or loaded.
Document any exception where vendor guidance marks the kernel unaffected.
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-50183 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
4Source 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.