Memory Leak of uid in Files Registration in io_uring

Kernel Updated 02 Oct 2025

Summary

24/04/2022
N/A
No i
Unrated
Not published

GSD-2022-1001751: io_uring: fix memory leak of uid in files registration. Affects Kernel versions >= 08a451739a9b5783f67de51e84cb6d9559bb9dc4, < 0853bd6885c2f293d88aaa7f7f1702c959b31680. 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 Penetration testing for web, API and mobile 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 is a high-performance I/O interface that allows applications to perform asynchronous I/O operations efficiently. It is a feature introduced in the Linux Kernel version 5.5. The io_uring provides a scalable and efficient interface for handling I/O operations, improving performance and reducing latency. However, a vulnerability has been discovered in the files registration process of io_uring, leading to a memory leak of the uid (user identifier).

Vulnerability Detail

The vulnerability in io_uring's files registration process results in a memory leak of the uid. When registering files with io_uring, the uid is not properly freed, causing a memory leak. This vulnerability can be exploited by an attacker to exhaust system memory resources, potentially leading to denial of service or other security issues. The vulnerability was introduced in Linux Kernel version 5.5 and has been fixed in version 5.15.33.

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 known workaround for this vulnerability. It is essential to update the Linux Kernel to the fixed version to mitigate the risk of memory leaks.

Conclusion

In conclusion, the memory leak of uid in the files registration process of io_uring can lead to memory exhaustion and potential security issues. It is crucial to update the Linux Kernel to version 5.15.33 or later to mitigate this vulnerability. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for Kernel →

Share this vulnerability

FAQ

io_uring is a high-performance I/O interface introduced in the Linux Kernel version 5.5. It provides an efficient and scalable interface for handling asynchronous I/O operations.

The vulnerability can lead to a memory leak of the uid in the files registration process of io_uring. This can potentially exhaust system memory resources and result in denial of service or other security issues.

To fix this vulnerability, it is recommended to update the Linux Kernel to version 5.15.33 or later, as this version includes the necessary fix to address the memory leak issue.

No, there is no known workaround for this vulnerability. Updating the Linux Kernel to the fixed version is the recommended solution.

The vulnerability was introduced in Linux Kernel version 5.5 and fixed in version 5.15.33.

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