Vulnerability in Kernel: rxrpc listen() Prealloc Rings

Kernel Updated 02 Oct 2025

Summary

28/06/2022
N/A
No i
Unrated
Not published

GSD-2022-1004007: rxrpc: Fix listen() setting the bar too high for the prealloc rings. Affects Kernel versions >= 00e907127e6f86d0f9b122d9b4347a8aa09a8b61, < 616f76498d5ddf26b997caf64a95cda3c8a55533. 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

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.

Sponsored Devnack Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

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. The issue arises from a flaw 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 denial-of-service (DoS) attacks or memory corruption. By setting the bar too high, the function fails to properly handle incoming connections, causing resource exhaustion or memory corruption. This can result in system instability, crashes, or unauthorized access to sensitive information. The vulnerability was introduced in Kernel version v4.9 and fixed in v4.14.283.

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. However, as a general best practice, it is advisable to implement proper network security measures, such as firewall rules and network segmentation, to mitigate the risk of potential attacks.

Conclusion

The vulnerability in the Kernel's rxrpc module's listen() function can lead to various security and stability issues. It is crucial to update the Linux Kernel to version v4.14.283 or later to mitigate the risk. Implementing proper network security measures is also recommended. For further assistance and support in vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for Kernel →

Share this vulnerability

FAQ

The vulnerability can lead to denial-of-service (DoS) attacks, system instability, crashes, or unauthorized access to sensitive information.

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

Yes, the vulnerability has been fixed in Linux Kernel version v4.14.283. It is recommended to update to this version or later to mitigate the risk.

At the time of this report, no known exploits for this vulnerability have been reported. However, it is important to apply the necessary updates and security measures to protect against potential attacks.

The vulnerability was discovered by the Linux Kernel security team during routine security audits and was subsequently fixed in the Kernel's codebase.

Related vulnerabilities

Recent vulnerabilities recorded for Kernel.

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 →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback