Vulnerability in Kernel package: RDMA/rxe: Clear all QP fields if creation failed
Summary
GSD-2021-1000516: RDMA/rxe: Clear all QP fields if creation failed. Affects Kernel versions >= 8700e3e7c4857d28ebaa824509934556da0b3e76, < a62225d951d77eb20208fed8fc199e0c9b1df08b. 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 package is an essential component of the Linux operating system, responsible for managing the system's core functions and providing an interface between hardware and software. It includes various subsystems, such as networking, memory management, and device drivers. The RDMA (Remote Direct Memory Access) subsystem within the Kernel enables efficient data transfer between remote systems without involving the CPU. The RDMA/rxe module specifically provides support for RDMA over Ethernet. However, a vulnerability has been identified in the RDMA/rxe module that could potentially lead to security issues.
Vulnerability Detail
The vulnerability in the RDMA/rxe module arises from a failure to clear all Queue Pair (QP) fields when the creation of a QP fails. This oversight can result in uninitialized or stale data being present in the QP fields, which may be exploited by an attacker to gain unauthorized access or execute arbitrary code. The impact and attack plausibility of this vulnerability have not been proven yet. It is important to note that this vulnerability affects the Linux Kernel versions from v4.8 to v5.4.122.
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 vulnerability in the RDMA/rxe module of the Kernel package can potentially lead to security issues if successfully exploited. It is crucial to update the Linux Kernel to version v5.4.122 or later to mitigate this vulnerability. For further support and assistance in vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
The impact of this vulnerability is not yet proven. However, if successfully exploited, it could potentially lead to unauthorized access or arbitrary code execution.
The vulnerability affects Linux Kernel versions from v4.8 to v5.4.122.
Yes, the vulnerability has been fixed in Linux Kernel version v5.4.122 by commit a62225d951d77eb20208fed8fc199e0c9b1df08b.
No known exploits for this vulnerability have been reported at this time.
You can use the Vulert Playground (https://vulert.com/scanner) to check if your system is affected by this vulnerability. It analyzes the manifest file (e.g., package-lock.json) of your application and provides real-time alerts for open-source vulnerabilities.
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
