rxrpc: Fix rxrpc_local leak in rxrpc_lookup_peer() - Kernel
Summary
GSD-2021-1002450: rxrpc: Fix rxrpc_local leak in rxrpc_lookup_peer(). Affects Kernel versions >= 9ebeddef58c41bd700419cdcece24cf64ce32276, < 3e70e3a72d80b16094faccbe438cd53761c3503a. 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 functionalities and acts as an interface between hardware and software. It manages system resources, facilitates communication between different software components, and ensures the overall stability and security of the system. The rxrpc module is responsible for handling the Remote Procedure Call (RPC) protocol over UDP/IP. It allows processes on different machines to communicate with each other by invoking procedures remotely. However, a vulnerability has been identified in the rxrpc_lookup_peer() function, which can lead to a local memory leak in the rxrpc_local structure.
Vulnerability Detail
The vulnerability in the rxrpc_lookup_peer() function can result in a local memory leak in the rxrpc_local structure. This can be exploited by an attacker to exhaust system resources, potentially leading to a denial-of-service (DoS) condition. The vulnerability was introduced in version v5.4 of the Linux Kernel and has been fixed in version v5.4.164. The impact and attack plausibility of this vulnerability have not been proven yet.
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 at the moment.
Conclusion
The rxrpc_lookup_peer() function in the Kernel's rxrpc module has a vulnerability that can result in a local memory leak. It is recommended to update the Linux Kernel to version v5.4.164 or later to fix this issue. If you need further assistance or support in addressing this vulnerability, please contact DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
The vulnerability can potentially lead to a denial-of-service (DoS) condition by exhausting system resources.
You can use the Vulert Playground (https://vulert.com/scanner) to check if your system is affected by this vulnerability. Simply upload your package-lock.json file and it will provide real-time alerts for open-source vulnerabilities.
No, there is currently no known exploit for this vulnerability.
No, this vulnerability can only be exploited locally.
There is no evidence of this vulnerability being actively exploited in the wild at the moment.
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
