Memory Leak in net/mlx5e Package
Summary
GSD-2021-1002085: net/mlx5e: Fix memory leak in mlx5_core_destroy_cq() error path. Affects Kernel versions >= e126ba97dba9edeb6fafa3665b5f8497fc9cdf8c, < ed8aafea4fec9c654e63445236e0b505e27ed3a7. No fix is published. How to fix ↓
Check if this vulnerability affects your application
Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.
No signup required · Results in about 60 seconds
Background
The net/mlx5e package is a component of the Linux Kernel, which is responsible for managing Mellanox network adapters. It provides the necessary drivers and functionality for these adapters to communicate with the operating system. The package is widely used in various Linux distributions and is critical for networking operations.
Vulnerability Detail
The vulnerability identified in the net/mlx5e package is related to a memory leak in the mlx5_core_destroy_cq() error path. When certain error conditions occur during the destruction of a completion queue (CQ), memory resources are not properly released, leading to a memory leak. This vulnerability can potentially be exploited by an attacker to exhaust system memory, resulting in denial-of-service conditions or other unpredictable behavior. The vulnerability was introduced in version v3.11 of the Linux Kernel and has been fixed in version v5.14.14.
How To Fix
No fixed version is published for this vulnerability.
Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →
Workaround
As a workaround, users can avoid triggering the error path that leads to the memory leak by ensuring proper error handling in applications or scripts that interact with the net/mlx5e package. This may involve implementing appropriate error checks and handling mechanisms to prevent the destruction of a CQ from encountering the specific error conditions that trigger the memory leak.
Conclusion
The memory leak vulnerability in the net/mlx5e package can have serious consequences, including system instability and denial-of-service conditions. It is crucial to update the Linux Kernel to the fixed version or apply appropriate workarounds to mitigate the risk. For further support and assistance in vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
The vulnerability can result in a memory leak, potentially leading to system instability, resource exhaustion, or denial-of-service conditions.
You can use the Vulert Playground at Vulert Scanner to check if your system is affected by this vulnerability. Simply upload your package-lock.json file, and Vulert will analyze it for any known vulnerabilities, including this memory leak issue.
At the time of this report, there is no known public exploit for this vulnerability. However, it is important to apply the recommended fix to mitigate any potential risks.
This vulnerability requires local access to the system or an application with privileges to interact with the net/mlx5e package. Remote exploitation is unlikely unless an attacker already has control over the affected system.
The primary solution is to update the Linux Kernel to the fixed version. However, if updating is not immediately feasible, implementing proper error handling in applications or scripts that interact with the net/mlx5e package can help mitigate the risk of triggering the memory leak.
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
