LiveActive security incident?Get immediate response
CVE Record

CVE-2022-50209: meson-mx-socinfo: Fix refcount leak in meson_mx_socinfo_init

In the Linux kernel, the following vulnerability has been resolved: meson-mx-socinfo: Fix refcount leak in meson_mx_socinfo_init of_find_matching_node() 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 analysislow

Security readout for executives and security teams

Plain-English summary

This is a Linux kernel bookkeeping bug in the Meson MX SoC information code. A device-tree node reference is not released after use, causing a reference-count leak. Sources do not provide CVSS, business impact, or exploitation evidence. Treat it as low-urgency patch hygiene unless you operate affected embedded Linux platforms.

Executive priority

Low priority for most organizations. Include it in normal kernel update cycles, with higher attention for managed embedded fleets or products built on affected Linux kernels.

Technical view

meson_mx_socinfo_init uses of_find_matching_node(), which increments a device-tree node reference count. The resolved issue adds the missing of_node_put() call when the node is no longer needed. The CVE record lists Linux kernel versions and stable commits, but provides no CWE, CVSS, or exploitation detail.

Likely exposure

Exposure appears limited to Linux systems running affected kernel versions with the Meson MX SoC information path present, most plausibly embedded or appliance platforms using relevant Amlogic Meson hardware. Standard servers and cloud workloads are less likely exposed unless they carry this kernel code path.

Exploitation context

The supplied sources do not show active exploitation, public exploit activity, or KEV listing. The described flaw is a reference-count leak during kernel initialization, not a documented privilege escalation or remote attack path.

Researcher notes

Evidence is sparse: no CVSS, CWE, exploit status, or operational impact is provided. The strongest source detail is the kernel fix description tying the issue to an unreleased device-tree node reference from of_find_matching_node().

Mitigation direction

  • Review vendor or distribution kernel advisories for CVE-2022-50209.
  • Update affected Linux kernels to builds containing the referenced stable fixes.
  • Prioritize embedded Linux and appliance images using Meson MX hardware.
  • Track the issue as maintenance unless vendor guidance raises severity.

Validation and detection

  • Inventory Linux kernel versions across embedded and appliance assets.
  • Check whether affected systems include the Meson MX SoC information code path.
  • Confirm the kernel source or package includes the missing of_node_put() fix.
  • Document systems where vendor kernels have not yet shipped the fix.
Prepared
Confidence
medium
Sources
9

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-50209 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
8Source 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
LinuxLinux5e68c0fc8df8a588b15cd469b27b8b5dbfadc6c3, 5e68c0fc8df8a588b15cd469b27b8b5dbfadc6c3, 5e68c0fc8df8a588b15cd469b27b8b5dbfadc6c3, 5e68c0fc8df8a588b15cd469b27b8b5dbfadc6c3, 5e68c0fc8df8a588b15cd469b27b8b5dbfadc6c3, 5e68c0fc8df8a588b15cd469b27b8b5dbfadc6c3, 5e68c0fc8df8a588b15cd469b27b8b5dbfadc6c3unaffected
LinuxLinux4.15, 0, 4.19.256, 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.