Memory Leak in RDMA/cma in Linux Kernel
Summary
GSD-2021-1001219: RDMA/cma: Fix rdma_resolve_route() memory leak. Affects Kernel versions < 07583ba2e2d8947c3d365d97608cb436510885ac. 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 Linux Kernel is the core component of the Linux operating system, responsible for managing system resources and providing an interface for applications to interact with the hardware. RDMA (Remote Direct Memory Access) is a technology that allows for high-speed data transfer between remote systems without involving the CPU. RDMA/cma (RDMA Connection Manager) is a component of the Linux Kernel that handles the establishment and management of RDMA connections. This vulnerability affects the RDMA/cma component in the Linux Kernel.
Vulnerability Detail
The vulnerability in RDMA/cma is related to a memory leak issue in the rdma_resolve_route() function. When this function is called to resolve the route for an RDMA connection, it may fail to release allocated memory in certain scenarios, leading to a memory leak. An attacker could potentially exploit this vulnerability to exhaust system memory resources, causing a denial-of-service condition. The impact and attack plausibility of this vulnerability have not been proven.
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
There is no specific workaround mentioned for this vulnerability.
Conclusion
In conclusion, the RDMA/cma component in the Linux Kernel is vulnerable to a memory leak issue in the rdma_resolve_route() function. This vulnerability can potentially lead to a denial-of-service condition. Users are advised to update their Linux Kernel to version v5.13.3 or later to fix this vulnerability. For further support on vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
The impact of this vulnerability is a potential denial-of-service condition due to memory exhaustion.
You can use the Vulert Playground (https://vulert.com/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 open-source vulnerabilities, including this one.
No known exploit for this vulnerability has been reported at the moment.
The recommended mitigation is to update the Linux Kernel to version v5.13.3 or later, which includes the fix for this vulnerability.
You can find more information about this vulnerability in the GSD database entry: https://github.com/cloudsecurityalliance/gsd-database/blob/main/2021/1001xxx/GSD-2021-1001219.json
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
