Menu

Star on GitHub · 3.2k

CVE-2022-50703

In the Linux kernel, the following vulnerability has been resolved: soc: qcom: smsm: Fix refcount leak bugs in qcom_smsm_probe() There are two refcount leak bugs in qcom_smsm_probe(): (1) The 'l…

Published Dec 24, 2025EPSS 0.23%

Overview

CVE-2022-50703 is a known-severity vulnerability. It was published on December 24, 2025.

Technical description

In the Linux kernel, the following vulnerability has been resolved:

soc: qcom: smsm: Fix refcount leak bugs in qcom_smsm_probe()

There are two refcount leak bugs in qcom_smsm_probe():

(1) The 'local_node' is escaped out from for_each_child_of_node() as

the break of iteration, we should call of_node_put() for it in error

path or when it is not used anymore.

(2) The 'node' is escaped out from for_each_available_child_of_node()

as the 'goto', we should call of_node_put() for it in goto target.

Remediation

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

Frequently asked questions

What is CVE-2022-50703?

CVE-2022-50703 is a known-severity vulnerability. It was published on December 24, 2025.

How severe is CVE-2022-50703?

CVSS score information is not yet available for this vulnerability. Check back as the CVE record is updated by NVD analysts.

How do I fix or remediate CVE-2022-50703?

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2022-50703?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2022-50703 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.