LiveActive security incident?Get immediate response
CVE Record

CVE-2022-50108: mfd: max77620: Fix refcount leak in max77620_initialise_fps

In the Linux kernel, the following vulnerability has been resolved: mfd: max77620: Fix refcount leak in max77620_initialise_fps of_get_child_by_name() returns a node pointer with refcount incremented, we should use of_node_put() on it when not need anymore. Add missing of_node_put() to avoid refcount leak.

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

Security readout for executives and security teams

Plain-English summary

CVE-2022-50108 is a Linux kernel resource-management bug in the max77620 driver. The described issue is a missing reference release, which can leak kernel object references over time. The provided sources do not include CVSS, CWE, impact detail, or active exploitation evidence.

Executive priority

Handle through normal kernel patch governance unless the organization relies on affected embedded Linux platforms. There is no source-supported evidence of active exploitation or severe business impact, but affected kernels should still receive vendor-supported updates.

Technical view

In max77620_initialise_fps, of_get_child_by_name() returns a device-tree node with an incremented reference count. The fix adds of_node_put() when the node is no longer needed, preventing a refcount leak. The CVE lists affected Linux kernel versions and multiple stable kernel fix commits.

Likely exposure

Exposure appears limited to Linux systems running affected kernel versions where the max77620 MFD driver code path is present or used. The sources do not show broad remote exposure, affected distributions, or vulnerable configurations beyond Linux kernel version and commit references.

Exploitation context

The source bundle does not cite known exploitation, proof-of-concept availability, or CISA KEV inclusion. Treat this as a kernel maintenance vulnerability unless vendor advisories provide stronger impact or exploitation evidence.

Researcher notes

Evidence is narrow: the CVE describes a refcount leak and points to stable kernel commits. No CVSS vector, CWE, crash behavior, privilege boundary, exploitability analysis, or runtime trigger conditions are provided in the bundle.

Mitigation direction

  • Apply the relevant Linux stable kernel update containing the referenced fixes.
  • Check distribution vendor advisories for backported patches and package status.
  • Prioritize systems using the max77620 kernel driver or affected embedded platforms.
  • Track the CVE record for later CVSS, CWE, or impact updates.

Validation and detection

  • Inventory Linux kernel versions against the affected versions listed in the CVE.
  • Confirm kernel source or package changelog includes the referenced stable fix commit.
  • Determine whether the max77620 driver is enabled in deployed kernels.
  • Review vendor kernel advisories for distro-specific affected and fixed package versions.
Prepared
Confidence
medium
Sources
8

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-50108 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
7Source 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
LinuxLinux327156c593600e0f08575621c2a56f311d482e7a, 327156c593600e0f08575621c2a56f311d482e7a, 327156c593600e0f08575621c2a56f311d482e7a, 327156c593600e0f08575621c2a56f311d482e7a, 327156c593600e0f08575621c2a56f311d482e7a, 327156c593600e0f08575621c2a56f311d482e7aunaffected
LinuxLinux4.7, 0, 5.4.211, 5.10.137, 5.15.61, 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.