Vulnerability in Kernel: rxrpc listen() Prealloc Rings

Kernel Updated 02 Oct 2025

Summary

28/06/2022

Disclosed on

N/A

Severity

No i

Fix available

Unrated

Severity

Not published

CVSS Score

GSD-2022-1003077: rxrpc: Fix listen() setting the bar too high for the prealloc rings. Affects Kernel versions >= 00e907127e6f86d0f9b122d9b4347a8aa09a8b61, < 369de57492c4f1a42563c5a3bd365822ca3bfc79. No fix is published. How to fix ↓

Free scan

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.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or Browse

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats

SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml

Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile

Javascript package-lock.json · yarn.lock · pnpm-lock.yaml

PHP composer.lock

Python poetry.lock · requirements.txt · Pipfile.lock

Go go.mod

Rust Cargo.lock

Ruby Gemfile.lock

Dart pubspec.lock

C/C++ conan.lock

Elixir mix.lock

Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Background

The Kernel is a critical component of the Linux operating system, responsible for managing system resources and facilitating communication between hardware and software. It provides essential functionality for the proper functioning of the system. The vulnerability in question affects the rxrpc module, which is responsible for providing a reliable, connection-oriented protocol over UDP. This vulnerability specifically impacts the 'listen()' function within the rxrpc module, which sets the bar too high for the preallocated rings. This vulnerability was introduced in version v4.9 of the Linux Kernel and has been fixed in version v5.17.14.

Vulnerability Detail

The vulnerability arises from the 'listen()' function in the rxrpc module, which incorrectly sets the bar too high for the preallocated rings. This can lead to various issues and potential security vulnerabilities. The exact impact and attack plausibility have not been proven yet. However, it is crucial to address this vulnerability to ensure the stability and security of the system. The vulnerability was introduced in version v4.9 of the Linux Kernel and has been fixed in version v5.17.14.

How To Fix

No fixed version is published for this vulnerability.

To fix this vulnerability, it is recommended to update the Linux Kernel to version v5.17.14 or later. This can be done by obtaining the updated Kernel source code from the official Linux Kernel repository (https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/) and compiling it for the target system. Alternatively, users can wait for their Linux distribution to provide an updated package containing the fixed Kernel version.

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. However, users can mitigate the risk by ensuring they have appropriate security measures in place, such as network segmentation, access controls, and monitoring for any suspicious activity.

Conclusion

The vulnerability in the Kernel's rxrpc module, specifically in the 'listen()' function, sets the bar too high for the preallocated rings. This can lead to potential security vulnerabilities and compromise the stability of the system. It is crucial to update the Linux Kernel to version v5.17.14 or later to fix this vulnerability. Users can also implement general security measures to mitigate the risk. For further support on vulnerability remediation, you can reach out to DevNack.com.

See every vulnerability recorded for Kernel →

FAQ

What is the impact of this vulnerability?

The exact impact of this vulnerability is yet to be proven. However, it has the potential to lead to security vulnerabilities and compromise the stability of the system.

How can I check if my system is affected by this vulnerability?

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 Vulert Playground will provide real-time monitoring and alerts for open-source vulnerabilities.