VYPR
Unrated severityNVD Advisory· Published Dec 24, 2025· Updated Apr 15, 2026

CVE-2022-50703

CVE-2022-50703

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.

AI Insight

LLM-synthesized narrative grounded in this CVE's description and references.

CVE-2022-50703 fixes two refcount leak bugs in the Linux kernel's Qualcomm SMSM driver probe function.

Root

Cause

The Linux kernel's Qualcomm Shared Memory State Machine (SMSM) driver contains two reference-count leak bugs in the qcom_smsm_probe() function. The first leak occurs when the local_node variable exits a for_each_child_of_node() loop early via a break statement; the driver fails to call of_node_put() on that node in the error path or after use. The second leak involves the node variable, which escapes a for_each_available_child_of_node() loop via a goto statement; the function's error-handling target also omits the necessary of_node_put() call for that node. [1]

Attack

Surface and Exploitation

Both bugs are triggered during device probe, meaning an attacker would need to influence device tree binding or module loading to reach the vulnerable code path. No authentication or special privileges are required beyond the ability to cause the driver to probe with a crafted or malformed device-tree entry. The vulnerability is local to the kernel and requires physical or logical access to the system's device tree configuration (e.g., through a device tree overlay or a platform device that uses the SMSM driver). [2]

Impact

If exploited, the reference-count leaks can lead to object lifetime mismanagement, potentially causing memory corruption, use-after-free conditions, or a denial of service (system crash or instability). An attacker who can control the device tree or hot-plug mechanisms might be able to trigger the leaks repeatedly to exhaust kernel memory or corrupt driver state. [3]

Mitigation

Patches have been backported to stable kernel releases. Users should update to kernels that include the fix, identified by commits referenced in the stable git tree [4]. No workaround is available; applying the patch is the recommended mitigation.

AI Insight generated on May 19, 2026. Synthesized from this CVE's description and the cited reference URLs; citations are validated against the source bundle.

Affected products

1

Patches

9

Vulnerability mechanics

Generated on May 9, 2026. Inputs: CWE entries + fix-commit diffs from this CVE's patches. Citations validated against bundle.

References

9

News mentions

0

No linked articles in our index yet.