BaseFortify

Publication date: 2025-10-04

Last updated on: 2026-01-23

Assigner: kernel.org

Description

In the Linux kernel, the following vulnerability has been resolved: memory: pl353-smc: Fix refcount leak bug in pl353_smc_probe() The break of for_each_available_child_of_node() needs a corresponding of_node_put() when the reference 'child' is not used anymore. Here we do not need to call of_node_put() in fail path as '!match' means no break. While the of_platform_device_create() will created a new reference by 'child' but it has considered the refcounting.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published

2025-10-04

Last Modified

2026-01-23

Generated

2026-07-06

AI Q&A

2025-10-04

EPSS Evaluated

2026-07-05

NVD

CVE-2022-50480

Affected Vendors & Products

Vendor	Product	Version / Range
linux	linux_kernel	From 5.0 (inc) to 5.4.220 (exc)
linux	linux_kernel	From 5.5 (inc) to 5.10.150 (exc)
linux	linux_kernel	From 5.11 (inc) to 5.15.75 (exc)
linux	linux_kernel	From 5.16 (inc) to 5.19.17 (exc)
linux	linux_kernel	From 6.0 (inc) to 6.0.3 (exc)

Helpful Resources

Exploitability

CWE

KEV

CWE ID	Description
CWE-NVD-CWE-Other

Attack-Flow Graph

Executive Summary

This vulnerability is a reference count leak bug in the Linux kernel's pl353-smc driver, specifically in the pl353_smc_probe() function. It involves improper handling of device tree node references where a corresponding of_node_put() call is missing when a reference to a child node is no longer needed, potentially leading to resource leaks.

Impact Analysis

The impact of this vulnerability is a resource leak in the kernel due to improper reference counting. This could lead to increased memory usage or instability in the system over time if the leak accumulates, potentially affecting system reliability.

Hi! I’m here to help you understand CVE-2022-50480. Ask me anything about the vulnerability, its impact, or mitigation strategies.

0/70