rxrpc: Fix call timer start racing with call destruction in Kernel
Summary
GSD-2022-1001752: rxrpc: Fix call timer start racing with call destruction. Affects Kernel versions >= a158bdd3247b9656df36ba133235fff702e9fdc3, < 8cbf4ae7a2833767d63114573e5f9a45740cc975. 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 crucial component of the Linux operating system that acts as a bridge between the hardware and software layers. It provides essential services and functionalities to enable the proper functioning of the system. The rxrpc module in the Kernel is responsible for managing the Remote Procedure Call (RPC) protocol over UDP/IP. This protocol is used for communication between networked devices. However, a vulnerability has been identified in the rxrpc module that can lead to a race condition between the start of a call timer and the destruction of the call itself.
Vulnerability Detail
The vulnerability in the rxrpc module occurs when a call timer is started concurrently with the destruction of the call. This race condition can result in various issues, including memory corruption or use-after-free vulnerabilities. An attacker could potentially exploit this vulnerability to execute arbitrary code or cause a denial-of-service (DoS) condition. The vulnerability was introduced in version v4.15 of the Kernel and has been fixed in version v5.15.33.
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 known workaround for this vulnerability. It is essential to apply the patch or update the Kernel to the fixed version as soon as possible.
Conclusion
The rxrpc module in the Kernel is vulnerable to a race condition between the start of a call timer and the destruction of the call. This can lead to memory corruption or use-after-free vulnerabilities, potentially enabling an attacker to execute arbitrary code or cause a DoS condition. It is crucial to update the Kernel to version v5.15.33 or later to mitigate this vulnerability. For further support on vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
The vulnerability can potentially lead to memory corruption or use-after-free vulnerabilities, which can be exploited by an attacker to execute arbitrary code or cause a denial-of-service (DoS) condition.
You can use the Vulert Playground at Vulert Scanner to check if your system is affected by this vulnerability. Simply upload your package-lock.json file to the playground, and it will provide real-time alerts for any open-source vulnerabilities, including this one.
No, there is no known workaround for this vulnerability. It is crucial to update the Kernel to the fixed version.
The vulnerability was introduced in version v4.15 of the Kernel. All versions between v4.15 and v5.15.32 are affected. The fix is available in version v5.15.33 and later.
You can find more information about this vulnerability in the Open Source Vulnerability Database (OSVDB) entry with ID GSD-2022-1001752 at https://github.com/cloudsecurityalliance/gsd-database/blob/main/2022/1001xxx/GSD-2022-1001752.json
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
