CVE-2022-50038: drm/meson: Fix refcount bugs in meson_vpu_has_available_connectors()
In the Linux kernel, the following vulnerability has been resolved:
drm/meson: Fix refcount bugs in meson_vpu_has_available_connectors()
In this function, there are two refcount leak bugs:
(1) when breaking out of for_each_endpoint_of_node(), we need call
the of_node_put() for the 'ep';
(2) we should call of_node_put() for the reference returned by
of_graph_get_remote_port() when it is not used anymore.
Security readout for executives and security teams
Plain-English summary
CVE-2022-50038 is a Linux kernel issue in the Meson DRM/VPU display connector logic. The source describes reference-count leaks, which can leave kernel object references unreleased. The provided data does not include a CVSS score, impact rating, or evidence of active exploitation.
Executive priority
Treat as a kernel maintenance item, not an emergency, based on current evidence. Patch through normal kernel update cycles, with priority for devices using the affected Meson display stack.
Technical view
The flaw is in meson_vpu_has_available_connectors(). The fix adds missing of_node_put() calls for endpoint references and for references returned by of_graph_get_remote_port(). The CVE source identifies Linux kernel versions and stable kernel commits, but does not describe attacker prerequisites or a complete impact chain.
Likely exposure
Exposure is most relevant to Linux systems running affected kernels with the Meson DRM/VPU driver path present. Confirm using the exact kernel version, vendor backports, and whether referenced stable fixes are included.
Exploitation context
The provided source bundle marks KEV as false and gives no public exploitation evidence. It also does not describe exploitability, required privileges, or whether the leak can cause denial of service in practice.
Researcher notes
Evidence is limited to the CVE record and kernel stable fixes. The bug is a reference-count leak in device-tree graph handling. No CWE, CVSS, exploitability assessment, or operational impact detail is provided.
Mitigation direction
Apply a kernel update containing the referenced stable fix commits.
Use distribution or device-vendor kernel advisories for backported fix status.
Prioritize systems using the Meson DRM/VPU display driver path.
Track this as lower urgency until vendor impact details are available.
Validation and detection
Inventory Linux kernel versions across affected systems.
Check whether vendor kernels include the listed stable commits.
Confirm Meson DRM/VPU driver exposure in relevant device builds.
Review kernel logs and stability reports for display-driver anomalies.
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-50038 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
8Source 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:01 UTC (UTC+00:00)
CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.