Race Condition Vulnerability in IB/rdmavt Package
Summary
GSD-2022-1001360: IB/rdmavt: add lock to call to rvt_error_qp to prevent a race condition. Affects Kernel versions >= d757c60eca9b22f4d108929a24401e0fdecda0b1, < 77ffb2495a41098f9d6a14f8aefde3188da75944. 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 IB/rdmavt package is a component of the Linux Kernel ecosystem. It provides support for InfiniBand (IB) and RoCE (RDMA over Converged Ethernet) devices. The package enables efficient communication between nodes in high-performance computing clusters. However, a race condition vulnerability has been identified in the package, which could lead to potential security risks.
Vulnerability Detail
The race condition vulnerability in the IB/rdmavt package arises from a missing lock in the call to rvt_error_qp. This can result in a race condition where multiple threads or processes access the same resource concurrently, leading to unexpected behavior or data corruption. Attackers may exploit this vulnerability to manipulate the state of the affected system, potentially gaining unauthorized access or causing denial of service. The vulnerability was introduced in version v5.1 of the Linux Kernel and has been fixed in version v5.16.20.
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 temporary workaround, it is possible to apply a patch or modify the affected code to include the missing lock manually. Here is an example of how the lock can be added:
// Add lock to call to rvt_error_qp
void rvt_error_qp(struct rvt_qp *qp)
{
spin_lock(&qp->lock);
// Existing code
spin_unlock(&qp->lock);
}
Conclusion
The race condition vulnerability in the IB/rdmavt package can pose significant security risks to systems utilizing this component. It is crucial to update the Linux Kernel to the fixed version v5.16.20 or later to mitigate these risks. Applying the recommended fixes and keeping the system up to date is essential for maintaining a secure environment. For further support on vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
The vulnerability can potentially be exploited by attackers to gain unauthorized access or cause denial of service on systems utilizing the IB/rdmavt package.
You can use the Vulert Playground (https://vulert.com/scanner) to check if your application or system is affected by this vulnerability. Simply upload your package-lock.json file to the playground and it will provide real-time alerts for open-source vulnerabilities.
At the time of this report, there is no known public exploit for this vulnerability. However, it is crucial to apply the recommended fixes to mitigate any potential risks.
The recommended workaround is to apply the provided patch or modify the code to include the missing lock manually. However, it is strongly advised to update to the fixed version of the Linux Kernel as soon as possible.
You can find more information about this vulnerability, including its technical details and the fix, in the official Linux Kernel repository (https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/).
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
