Memory Leak in RDMA/cm in Kernel
Summary
GSD-2022-1004444: RDMA/cm: Fix memory leak in ib_cm_insert_listen. Affects Kernel versions >= 98f67156a80f37db70ec64787020b1f9bc8aea8c, < 889000874c1204e47c7f2a4945db262a47e7efc9. 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 Kernel is a critical component of the Linux operating system that provides core functionality and facilitates communication between hardware and software. RDMA/cm (Remote Direct Memory Access/Connection Manager) is a subsystem within the Kernel that manages communication between InfiniBand and RoCE (RDMA over Converged Ethernet) devices. It enables efficient data transfer and low-latency communication between nodes in a high-performance computing environment. However, a vulnerability has been discovered in the RDMA/cm module that can lead to a memory leak.
Vulnerability Detail
The vulnerability, identified as GSD-2022-1004444, originates from a memory leak in the ib_cm_insert_listen function of the RDMA/cm module. This function is responsible for inserting a new listening connection into the RDMA connection manager's listen hash table. The memory leak occurs when the function fails to properly release allocated memory in certain error scenarios. An attacker could potentially exploit this vulnerability to exhaust system memory resources, leading to a denial-of-service condition or other unpredictable behavior. The impact and attack plausibility of this vulnerability have not yet 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 specific workaround has been mentioned for this vulnerability.
Conclusion
In conclusion, a memory leak vulnerability has been identified in the RDMA/cm module of the Linux Kernel. This vulnerability can potentially lead to a denial-of-service condition or other unpredictable behavior. It is crucial to update the Kernel to version v5.15.53 or a later one to mitigate 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 not yet proven, but it could potentially lead to a denial-of-service condition or other unpredictable behavior by exhausting system memory resources.
You can use tools like Vulert (https://vulert.com) to check if your system is affected by this vulnerability. Vulert monitors and alerts in real-time for open-source vulnerabilities without requiring access to the code or installation. Simply provide a manifest file like package-lock.json to Vulert's playground (https://vulert.com/scanner) to check if your application is affected.
No known exploit for this vulnerability has been reported at this time.
The recommended mitigation is to update the Kernel to version v5.15.53 or a later one that includes the fix for this vulnerability.
The vulnerability was discovered by an automated process and reported in the GSD database maintained by the Cloud Security Alliance.
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
