rxrpc: Fix call timer start racing with call destruction
Summary
GSD-2022-1002025: rxrpc: Fix call timer start racing with call destruction. Affects Kernel versions >= a158bdd3247b9656df36ba133235fff702e9fdc3, < 051360e51341cd17738d82c15a8226010c7cb7f6. 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 rxrpc package is a part of the Linux Kernel ecosystem. It provides support for the RxRPC protocol, which is used for remote procedure calls (RPC) over UDP. The package allows for efficient and reliable communication between networked systems. However, a vulnerability has been discovered in the package that can lead to a race condition between the start of a call timer and the destruction of the call. This vulnerability can potentially result in undefined behavior and may be exploited by attackers to disrupt or compromise the system.
Vulnerability Detail
The vulnerability in rxrpc arises due to a race condition between the start of a call timer and the destruction of the call. When a call is initiated, a timer is started to track its progress. However, if the call is destroyed before the timer starts, it can lead to undefined behavior. An attacker may be able to exploit this vulnerability by carefully timing their actions to trigger the race condition, potentially causing a denial-of-service (DoS) or other malicious outcomes. The vulnerability was introduced in version v4.15 of the Linux Kernel and has been fixed in version v5.10.110.
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 provided for this vulnerability. It is advised to apply the fix by updating the Linux Kernel to the recommended version.
Conclusion
The rxrpc package in the Linux Kernel is vulnerable to a race condition between the start of a call timer and the destruction of the call. This vulnerability can potentially lead to undefined behavior and may be exploited by attackers. It is crucial to update the Linux Kernel to version v5.10.110 or later to fix this vulnerability. For further support on vulnerability remediation, you can contact DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
The vulnerability can potentially lead to undefined behavior and may be exploited by attackers to disrupt or compromise the system. However, the actual impact and attack plausibility have not been proven.
You can use the Vulert Playground at Vulert Scanner to check if your system is affected by this vulnerability. Simply upload your manifest file (e.g., package-lock.json) and the playground will analyze it for any open-source vulnerabilities, including this one.
At the time of this report, no known exploit has been documented for this vulnerability. However, it is still important to apply the recommended fix to mitigate any potential risks.
No specific temporary measures have been provided for this vulnerability. It is recommended to update the Linux Kernel as soon as possible to ensure the security of your system.
You can find more information about this vulnerability in the official Linux Kernel repository. The vulnerability ID is GSD-2022-1002025, and the details can be accessed at https://github.com/cloudsecurityalliance/gsd-database/blob/main/2022/1002xxx/GSD-2022-1002025.json.
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
