LiveActive security incident?Get immediate response
CVE Record

CVE-2022-50112: rpmsg: qcom_smd: Fix refcount leak in qcom_smd_parse_edge

In the Linux kernel, the following vulnerability has been resolved: rpmsg: qcom_smd: Fix refcount leak in qcom_smd_parse_edge of_parse_phandle() returns a node pointer with refcount incremented, we should use of_node_put() on it when done.

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

Analyst readout for executives and security teams

Plain-English summary

CVE-2022-50112 is a Linux kernel defect in Qualcomm SMD rpmsg handling. The code failed to release a device-tree node reference after parsing it, creating a refcount leak. The source bundle does not provide CVSS, real-world impact, or evidence of attacks.

Executive priority

Handle through routine kernel and firmware patch management unless you operate Qualcomm-based embedded Linux fleets. The urgency is limited by missing severity data and no exploitation evidence, but unresolved kernel defects should not be ignored.

Technical view

The resolved issue is in qcom_smd_parse_edge. of_parse_phandle() increments a node pointer reference count, but the affected code did not call of_node_put() when finished. Kernel stable commits correct that lifecycle handling. Impact details beyond the leak are not provided.

Likely exposure

Exposure is most plausible on Linux systems using affected kernel versions and the Qualcomm SMD rpmsg driver. The bundle lists Linux as affected but does not identify distributions, appliances, cloud images, or specific Qualcomm-based products.

Exploitation context

The source bundle marks KEV as false and provides no cited evidence of active exploitation. It also does not describe exploit prerequisites, attacker position, privilege requirements, denial-of-service impact, or weaponized public exploitation.

Researcher notes

Evidence is narrow: a Linux stable refcount-leak fix, affected kernel version data, and no CVSS/CWE details. Treat product exposure carefully, because downstream vendors may backport fixes without changing visible version strings.

Mitigation direction

  • Apply a kernel update or vendor backport containing the referenced stable fixes.
  • Prioritize Linux assets using Qualcomm SMD rpmsg functionality.
  • Check distribution, device, or appliance vendor guidance for fixed kernel builds.
  • For embedded devices, request firmware updates from the device vendor.
  • If no vendor fix is named, track official Linux and vendor advisories.

Validation and detection

  • Inventory kernel versions against the affected versions listed in the CVE bundle.
  • Confirm whether the running kernel includes a referenced stable fix or backport.
  • Check whether qcom_smd rpmsg support is present or enabled on relevant assets.
  • Review vendor advisories for CVE-2022-50112 coverage and fixed builds.
  • After updating, verify the installed kernel or firmware maps to a fixed lineage.
Prepared
Confidence
medium
Sources
9

Public sources used

Based on public source material and reviewed before publication.

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-50112 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
LinuxLinux53e2822e56c7bc67e5dc19acb1e5fbb8ebff8614, 53e2822e56c7bc67e5dc19acb1e5fbb8ebff8614, 53e2822e56c7bc67e5dc19acb1e5fbb8ebff8614, 53e2822e56c7bc67e5dc19acb1e5fbb8ebff8614, 53e2822e56c7bc67e5dc19acb1e5fbb8ebff8614, 53e2822e56c7bc67e5dc19acb1e5fbb8ebff8614, 53e2822e56c7bc67e5dc19acb1e5fbb8ebff8614unaffected
LinuxLinux4.9, 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.