CVE-2023-54106
Unknown Unknown - Not Provided
Memory Leak in Linux Kernel mlx5e_init_rep_rx Component

Publication date: 2025-12-24

Last updated on: 2025-12-24

Assigner: kernel.org

Description
In the Linux kernel, the following vulnerability has been resolved: net/mlx5: fix potential memory leak in mlx5e_init_rep_rx The memory pointed to by the priv->rx_res pointer is not freed in the error path of mlx5e_init_rep_rx, which can lead to a memory leak. Fix by freeing the memory in the error path, thereby making the error path identical to mlx5e_cleanup_rep_rx().
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2025-12-24
Last Modified
2025-12-24
Generated
2026-05-07
AI Q&A
2025-12-24
EPSS Evaluated
2026-05-05
NVD
EUVD
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
linux linux_kernel *
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-UNKNOWN
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?

This vulnerability is a potential memory leak in the Linux kernel's mlx5 network driver. Specifically, the memory pointed to by the priv->rx_res pointer is not freed in the error path of the mlx5e_init_rep_rx function. This means that if an error occurs during initialization, allocated memory is not properly released, leading to a memory leak. The fix involves freeing this memory in the error path to prevent the leak.


How can this vulnerability impact me? :

The impact of this vulnerability is a potential memory leak in the Linux kernel's network driver. Over time, this could lead to increased memory usage and possibly degrade system performance or stability, especially on systems that frequently encounter errors in this code path. However, it does not directly lead to code execution or data exposure.


What immediate steps should I take to mitigate this vulnerability?

Apply the patch or update the Linux kernel to a version where the mlx5e_init_rep_rx function has been fixed to properly free memory in the error path, as described. This will prevent the memory leak issue.


Ask Our AI Assistant
Need more information? Ask your question to get an AI reply (Powered by our expertise)
0/70
EPSS Chart