Vulnerability in io_uring package: Add a schedule point in io_add_buffers()

Kernel Updated 02 Oct 2025

Summary

18/03/2022
N/A
No i
Unrated
Not published

GSD-2022-1000811: io_uring: add a schedule point in io_add_buffers(). Affects Kernel versions >= ddf0322db79c5984dc1a1db890f946dd19b7d6d9, < c718ea4e7382e18957ed0e88a5f855e2122d9c00. 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 io_uring package is a component of the Linux Kernel that provides an interface for asynchronous I/O operations. It allows applications to efficiently perform I/O operations without blocking the execution of other tasks. The package is widely used in Linux-based systems and is critical for high-performance I/O operations.

Vulnerability Detail

The vulnerability identified in the io_uring package involves the lack of a schedule point in the io_add_buffers() function. This omission can potentially lead to a denial-of-service (DoS) attack or other security exploits. An attacker could exploit this vulnerability to cause the system to become unresponsive or execute arbitrary code. The vulnerability was introduced in version v5.7 of the Linux Kernel and was fixed in version v5.15.26.

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 apply the patch manually by cherry-picking the commit (c718ea4e7382e18957ed0e88a5f855e2122d9c00) into their existing Kernel version. Here is an example of how to apply the patch using the git cherry-pick command:

git cherry-pick c718ea4e7382e18957ed0e88a5f855e2122d9c00

It is important to note that this workaround is not recommended for production environments and may introduce other issues. It is best to update the Kernel to the latest version.

Conclusion

In conclusion, the io_uring package in the Linux Kernel is vulnerable to a denial-of-service (DoS) attack and arbitrary code execution due to the absence of a schedule point in the io_add_buffers() function. To mitigate this vulnerability, it is crucial to update the Kernel to version v5.15.26 or later. Alternatively, users can apply the patch manually, but updating the Kernel is the recommended approach. For further support and assistance with vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for Kernel →

Share this vulnerability

FAQ

This vulnerability can potentially lead to a denial-of-service (DoS) attack or allow an attacker to execute arbitrary code on 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 and the Vulert Playground will analyze it for any open-source vulnerabilities, including this one.

At the time of this report, there is no known exploit for this vulnerability. However, it is important to patch the vulnerability as soon as possible to prevent any potential attacks.

The recommended mitigation is to update the Linux Kernel to version v5.15.26 or later. This update includes the necessary fix for the vulnerability.

Yes, you can apply the patch manually by cherry-picking the commit (c718ea4e7382e18957ed0e88a5f855e2122d9c00) into your existing Kernel version. However, it is recommended to update the Kernel to the latest version for better security and stability.

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