LiveActive security incident?Get immediate response
CVE Record

CVE-2022-50191: regulator: of: Fix refcount leak bug in of_get_regulation_constraints()

In the Linux kernel, the following vulnerability has been resolved: regulator: of: Fix refcount leak bug in of_get_regulation_constraints() We should call the of_node_put() for the reference returned by of_get_child_by_name() which has increased the refcount.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

CVE-2022-50191 is a Linux kernel bookkeeping flaw in regulator device-tree handling. A reference count is increased but not released, creating a leak. The public record does not provide CVSS, confirmed business impact, or exploit evidence, so urgency should be based on kernel exposure and vendor guidance.

Executive priority

Handle through normal kernel patch governance unless local vendors assign higher severity. There is no source-backed evidence of active exploitation, but kernel hygiene still matters because affected systems may be hard to patch later.

Technical view

The issue is in of_get_regulation_constraints(), where of_get_child_by_name() returns a referenced node and the code failed to call of_node_put(). Upstream stable commits correct that reference handling. The record lists Linux kernel versions as affected but gives no CWE, CVSS, attacker model, or demonstrated impact.

Likely exposure

Exposure is limited to systems running affected Linux kernel versions or downstream kernels that include the vulnerable regulator OF code path. The bundle does not show that ordinary network services are directly exposed.

Exploitation context

The CVE bundle marks KEV as false and provides no cited evidence of active exploitation, public exploit availability, or remote attack paths. Treat exploitation feasibility as unconfirmed.

Researcher notes

Evidence is sparse: the record describes a refcount leak and links stable commits, but omits CVSS, CWE, exploit prerequisites, and concrete impact. Further assessment should inspect downstream patches and affected kernel configurations.

Mitigation direction

  • Inventory Linux kernel versions across servers, appliances, and embedded systems.
  • Check distribution or vendor advisories for backported fixes to this kernel issue.
  • Apply vendor-supported kernel updates containing the referenced stable fixes.
  • Prioritize internet-facing and operationally critical Linux assets during patch planning.
  • Track unsupported kernels for replacement or isolation decisions.

Validation and detection

  • Compare running kernel versions against the affected entries in the CVE record.
  • Review vendor kernel changelogs for CVE-2022-50191 or the referenced upstream commits.
  • Confirm patched systems boot the expected updated kernel after maintenance.
  • For custom kernels, verify the relevant regulator OF patch is present.
  • Document any systems awaiting vendor guidance or maintenance windows.
Prepared
Confidence
medium
Sources
5

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-50191 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
9Source 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.

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux40e20d68bb3fb1ce2704c886d597918988d3321d, 40e20d68bb3fb1ce2704c886d597918988d3321d, 40e20d68bb3fb1ce2704c886d597918988d3321d, 40e20d68bb3fb1ce2704c886d597918988d3321d, 40e20d68bb3fb1ce2704c886d597918988d3321d, 40e20d68bb3fb1ce2704c886d597918988d3321d, 40e20d68bb3fb1ce2704c886d597918988d3321d, 40e20d68bb3fb1ce2704c886d597918988d3321dunaffected
LinuxLinux3.19, 0, 4.14.291, 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.