BaseFortify

Publication date: 2025-10-07

Last updated on: 2026-03-17

Assigner: kernel.org

Description

In the Linux kernel, the following vulnerability has been resolved: staging: rtl8723bs: fix a potential memory leak in rtw_init_cmd_priv() In rtw_init_cmd_priv(), if `pcmdpriv->rsp_allocated_buf` is allocated in failure, then `pcmdpriv->cmd_allocated_buf` will be not properly released. Besides, considering there are only two error paths and the first one can directly return, so we do not need implicitly jump to the `exit` tag to execute the error handler. So this patch added `kfree(pcmdpriv->cmd_allocated_buf);` on the error path to release the resource and simplified the return logic of rtw_init_cmd_priv(). As there is no proper device to test with, no runtime testing was performed.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published

2025-10-07

Last Modified

2026-03-17

Generated

2026-07-06

AI Q&A

2025-10-07

EPSS Evaluated

2026-07-05

NVD

CVE-2022-50513

Affected Vendors & Products

Vendor	Product	Version / Range
linux	linux_kernel	From 6.0 (inc) to 6.0.3 (inc)
linux	kernel	*

Helpful Resources

Exploitability

CWE

KEV

CWE ID	Description
CWE-401	The product does not sufficiently track and release allocated memory after it has been used, making the memory unavailable for reallocation and reuse.

Attack-Flow Graph

Executive Summary

This vulnerability is a potential memory leak in the Linux kernel's rtl8723bs staging driver, specifically in the function rtw_init_cmd_priv(). If a certain buffer (rsp_allocated_buf) is allocated but an error occurs, another buffer (cmd_allocated_buf) is not properly freed, leading to a memory leak. The patch fixes this by adding code to free the allocated buffer on error paths and simplifies the function's return logic.

Impact Analysis

The impact of this vulnerability is a potential memory leak in the Linux kernel driver, which could lead to increased memory usage and possibly degrade system performance or stability over time if the error condition occurs repeatedly.

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

0/70