Memory Leak in RDMA/cma in Linux Kernel
Summary
GSD-2021-1001352: RDMA/cma: Fix rdma_resolve_route() memory leak. Affects Kernel versions < 032c68b4f5be128a2167f35b558b7cec88fe4972. 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
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
Background
The Linux Kernel is a widely used open-source operating system kernel that serves as the foundation for various Linux distributions. It provides essential functionality for managing system resources, including memory, processes, and device drivers. 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 specifically affects the rdma_resolve_route() function in RDMA/cma.
Vulnerability Detail
The rdma_resolve_route() function in RDMA/cma in the Linux Kernel suffers from a memory leak. When this function is called to resolve the route for an RDMA connection, it fails to release allocated memory in certain scenarios, leading to a memory leak. An attacker could potentially exploit this vulnerability to exhaust system memory resources, resulting in 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
No workaround has been mentioned for this vulnerability.
Conclusion
The memory leak vulnerability in RDMA/cma in the Linux Kernel can be fixed by updating the kernel to version v5.4.133 or later. Users are advised to follow the provided instructions to update their Linux Kernel and mitigate the vulnerability. For further support on vulnerability remediation, you can contact DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
The impact of this vulnerability is a potential memory leak, which could lead to a denial-of-service condition if system memory resources are exhausted.
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 the Vulert Playground will analyze it for any open-source vulnerabilities, including this one.
No known exploit has been reported for this vulnerability at the time of this report.
The only known mitigation for this vulnerability is to update the Linux Kernel to version v5.4.133 or later.
You can find more information about this vulnerability in the official Linux Kernel repository (https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/) and the vulnerability database maintained by the Cloud Security Alliance (https://github.com/cloudsecurityalliance/gsd-database).
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
