Vulnerability in Kernel: rxrpc listen() Prealloc Rings
Summary
GSD-2022-1002722: rxrpc: Fix listen() setting the bar too high for the prealloc rings. Affects Kernel versions >= 00e907127e6f86d0f9b122d9b4347a8aa09a8b61, < e198f1930050e3115c80b67d9249f80f98a27c67. 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 functionality and interfaces with hardware devices. It manages system resources, facilitates communication between software and hardware, and supports various subsystems. The vulnerability affects the rxrpc module, which is responsible for providing a reliable, sequenced, and acknowledged datagram service over UDP/IP. The vulnerability arises from an issue in the listen() function, which sets the bar too high for the preallocated rings.
Vulnerability Detail
The vulnerability in the rxrpc module's listen() function allows an attacker to exploit the preallocated rings, potentially leading to a denial-of-service (DoS) attack or other security compromises. By setting the bar too high, the function can exhaust system resources, causing performance degradation or system instability. This vulnerability was introduced in Kernel version 4.9 and is fixed in version 5.18.3.
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 workaround, users can disable the rxrpc module if it is not required for their system. This can be achieved by modifying the Kernel configuration and rebuilding it without the rxrpc module. However, this workaround should only be considered if the module is not essential for system functionality.
Conclusion
The vulnerability in the Kernel's rxrpc module's listen() function can lead to resource exhaustion and potential security compromises. It is crucial to update the Linux Kernel to version 5.18.3 or later to mitigate this vulnerability. Users can also disable the rxrpc module as a temporary workaround if it is not essential for their system. For further support and assistance in vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
The vulnerability can lead to a denial-of-service (DoS) attack or system instability due to resource exhaustion.
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 the playground will analyze it for potential vulnerabilities.
At the time of this report, there is no known exploit for this vulnerability. However, it is crucial to apply the recommended fix to mitigate any potential risks.
As mentioned in the workaround section, you can disable the rxrpc module if it is not necessary for your system. However, it is recommended to apply the official fix as soon as possible.
You can refer to the official Linux Kernel repository (https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/) for more details about this vulnerability and the specific fix implemented.
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
