LiveActive security incident?Get immediate response
CVE Record

CVE-2022-50188: drm/meson: Fix refcount leak in meson_encoder_hdmi_init

In the Linux kernel, the following vulnerability has been resolved: drm/meson: Fix refcount leak in meson_encoder_hdmi_init of_find_device_by_node() takes reference, we should use put_device() to release it when not need anymore. Add missing put_device() in error path to avoid refcount leak.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysislow

Security readout for executives and security teams

Plain-English summary

This Linux kernel issue is a resource-management bug in the Meson HDMI display driver path. The sources describe a missing reference release on an error path, which can leak a device reference. No CVSS score, CWE, or active exploitation evidence is provided.

Executive priority

Treat this as routine kernel hygiene unless the organization operates Meson-based Linux devices at scale. Patch through normal kernel maintenance, with faster handling for embedded fleets where display-driver failures could affect operations.

Technical view

The fix adds a missing put_device() after of_find_device_by_node() in meson_encoder_hdmi_init. The vulnerable behavior is a reference-count leak in the drm/meson HDMI initialization error path. Public sources only identify Linux kernel fixes and affected Linux kernel versions; they do not describe exploitability impact.

Likely exposure

Exposure appears most relevant to Linux systems using the drm/meson HDMI driver, commonly associated with Meson-based platforms. Organizations should map affected kernel versions and vendor backports rather than assume all Linux systems are exposed.

Exploitation context

The provided sources do not report active exploitation, proof-of-concept code, or KEV listing. Based only on the description, this is an error-path refcount leak, so practical exploitation risk is unclear from public data.

Researcher notes

Evidence is limited to the CVE description and kernel stable references. The record lacks CVSS, CWE, exploit reports, and detailed affected-version semantics, so exposure assessment should be validated against actual kernel source, vendor packages, and device hardware.

Mitigation direction

  • Update to a vendor kernel containing the referenced stable fixes.
  • Prioritize Meson-based systems using the HDMI/display driver path.
  • Check distribution advisories for backported fixes before relying on version numbers.
  • If no package is available, follow vendor guidance for interim handling.

Validation and detection

  • Inventory Linux kernel versions across Meson-based devices.
  • Confirm whether the drm/meson HDMI driver is present or enabled.
  • Review vendor changelogs for the referenced stable commit IDs.
  • Track CVE status for any later CVSS, CWE, or exploitation updates.
Prepared
Confidence
medium
Sources
6

Public sources used

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-50188 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

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.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxe098989a9219f4456047f9b0e8c44f03e29a843e, 0af5e0b41110e2da872030395231ab19c45be931, 0af5e0b41110e2da872030395231ab19c45be931, 0af5e0b41110e2da872030395231ab19c45be931unaffected
LinuxLinux5.17, 0, 5.18.18, 5.19.2, 6.0affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.