Vulnerability in Kernel package: rxrpc: Fix listen() setting the bar too high for the prealloc rings
Summary
GSD-2022-1003767: rxrpc: Fix listen() setting the bar too high for the prealloc rings. Affects Kernel versions >= 00e907127e6f86d0f9b122d9b4347a8aa09a8b61, < 91b34bf0409f43bb60453bab23c5beadd726d022. 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 package is a crucial component of the Linux operating system, responsible for managing core system functions and providing an interface between hardware and software. It is a fundamental part of the system's infrastructure, facilitating communication between different software components and managing system resources. The vulnerability in question affects the rxrpc module within the Kernel package, specifically the listen() function. This function sets the threshold too high for the preallocated rings, potentially leading to resource exhaustion and denial-of-service attacks.
Vulnerability Detail
The vulnerability arises from a flaw in the listen() function of the rxrpc module. By setting the bar too high for the preallocated rings, an attacker can exploit this vulnerability to exhaust system resources, causing a denial-of-service condition. This vulnerability was introduced in version v4.9 of the Linux Kernel and has been fixed in version v5.4.198. 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 specific workaround mentioned for this vulnerability.
Conclusion
The vulnerability in the Kernel package's rxrpc module, specifically in the listen() function, can lead to resource exhaustion and denial-of-service attacks. It is crucial to update the Linux Kernel package to version v5.4.198 or later to mitigate this vulnerability. For further support and assistance in vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
The vulnerability can lead to resource exhaustion and denial-of-service attacks, potentially disrupting the normal functioning of the affected system.
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 to the playground, and it will provide real-time alerts for open-source vulnerabilities.
As of now, there is no known exploit for this vulnerability. However, it is important to apply the recommended fix to mitigate any potential risks.
Yes, this vulnerability can be exploited remotely by an attacker who can send specially crafted requests to the affected system.
The recommended solution is to update the Linux Kernel package to the fixed version. However, if updating is not feasible, implementing network-level mitigations and access controls can help reduce the risk of exploitation.
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
