LiveActive security incident?Get immediate response
CVE Record

CVE-2022-50196: soc: qcom: ocmem: Fix refcount leak in of_get_ocmem

In the Linux kernel, the following vulnerability has been resolved: soc: qcom: ocmem: Fix refcount leak in of_get_ocmem of_parse_phandle() 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. of_node_put() will check NULL pointer.

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 bookkeeping bug in the Qualcomm OCMEM driver. A device-tree node reference is not released after lookup, which can leak references over time. The public record does not provide CVSS, CWE, impact severity, or evidence of exploitation.

Executive priority

Do not treat this as an emergency from the available evidence. Include it in normal kernel patch management, with higher attention for Qualcomm-based embedded or appliance fleets where kernel updates may lag.

Technical view

In soc/qcom/ocmem, of_get_ocmem calls of_parse_phandle, which returns a node pointer with an incremented reference count. The fix adds of_node_put when the node is no longer needed. The issue is recorded as resolved in Linux stable commits across affected kernel lines.

Likely exposure

Exposure appears limited to systems running affected Linux kernels with the Qualcomm OCMEM driver path present or relevant. General Linux servers without that driver or hardware path are less likely to be exposed, but vendor kernel backports must be checked.

Exploitation context

The bundle marks KEV as false and provides no public evidence of active exploitation, exploit availability, or practical attack conditions. Treat exploitability as unproven from these sources.

Researcher notes

The record identifies a refcount leak, not a memory corruption primitive. No CVSS, CWE, or attack preconditions are supplied. Analysis should focus on driver reachability, kernel lineage, and whether downstream vendors have incorporated the stable fixes.

Mitigation direction

  • Apply Linux or device-vendor kernel updates containing the referenced stable fixes.
  • Check vendor advisories before assuming a specific downstream kernel is fixed.
  • Prioritize Qualcomm SoC fleets or products using the OCMEM driver.
  • Track backports if running long-term, embedded, or vendor-modified kernels.

Validation and detection

  • Inventory kernel versions and vendor kernel branches across affected assets.
  • Check whether the referenced stable commits or equivalent backports are present.
  • Confirm whether Qualcomm OCMEM support is enabled or used in relevant builds.
  • Document exceptions where vendor status is unavailable or not yet published.
Prepared
Confidence
medium
Sources
7

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-50196 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
6Source 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
LinuxLinux88c1e9404f1deee02e52d13aae3d9ee2cabd66f5, 88c1e9404f1deee02e52d13aae3d9ee2cabd66f5, 88c1e9404f1deee02e52d13aae3d9ee2cabd66f5, 88c1e9404f1deee02e52d13aae3d9ee2cabd66f5, 88c1e9404f1deee02e52d13aae3d9ee2cabd66f5unaffected
LinuxLinux5.5, 0, 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.