LiveActive security incident?Get immediate response
CVE Record

CVE-2022-50157: PCI: microchip: Fix refcount leak in mc_pcie_init_irq_domains()

In the Linux kernel, the following vulnerability has been resolved: PCI: microchip: Fix refcount leak in mc_pcie_init_irq_domains() of_get_next_child() returns a node pointer with refcount incremented, so we should use of_node_put() on it when we don't need it anymore. mc_pcie_init_irq_domains() only calls of_node_put() in the normal path, missing it in some error paths. 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

This CVE is a Linux kernel resource-management bug in the Microchip PCIe driver. Some error paths failed to release a device-tree node reference, causing a refcount leak. The public bundle does not provide CVSS, CWE, business impact, or evidence of exploitation, so urgency should be based on whether affected kernels and hardware are present.

Executive priority

Track and patch through normal kernel maintenance unless asset inventory shows critical systems using the affected Microchip PCIe path. There is no source-backed evidence of exploitation or severe impact in the provided bundle.

Technical view

mc_pcie_init_irq_domains() used of_get_next_child(), which increments a node reference count. Normal handling released it, but some error paths missed of_node_put(), creating a refcount leak. The referenced stable commits add the missing release calls. Impact details are not provided in the source bundle.

Likely exposure

Most relevant exposure is Linux systems using the Microchip PCIe controller driver on affected kernel versions. The bundle lists Linux as affected and references stable kernel fixes, but does not identify distributions, appliances, or cloud images.

Exploitation context

The bundle says this is not in KEV and provides no cited evidence of active exploitation, public exploit use, or weaponization. The issue appears to require the affected kernel code path and relevant hardware or configuration.

Researcher notes

The record is sparse: no CVSS, CWE, exploit status beyond non-KEV, or distribution mapping. Analysis should stay close to the upstream fix: a missing of_node_put() on error paths after of_get_next_child().

Mitigation direction

  • Inventory Linux kernels and identify systems using the Microchip PCIe driver.
  • Compare deployed kernel versions against vendor advisories and the referenced stable commits.
  • Apply the appropriate kernel update from your Linux distribution or kernel vendor.
  • If no packaged fix exists, monitor vendor guidance rather than applying ad hoc changes.

Validation and detection

  • Confirm whether affected systems include Microchip PCIe controller support.
  • Check kernel package changelogs for the referenced fix commits.
  • Verify updated systems are running the intended patched kernel after reboot.
  • Review operational telemetry for unusual kernel resource growth if exposure is confirmed.
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-50157 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
LinuxLinux6f15a9c9f94133bee0d861a4bf25e10aaa95219d, 6f15a9c9f94133bee0d861a4bf25e10aaa95219d, 6f15a9c9f94133bee0d861a4bf25e10aaa95219d, 6f15a9c9f94133bee0d861a4bf25e10aaa95219dunaffected
LinuxLinux5.12, 0, 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.