Critical io_uring Credential Assignment Vulnerability in Linux Kernel

linux Updated 02 Oct 2025

Summary

26/02/2025
N/A
Yes i
Unrated
Not published

CVE-2022-49056: Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority. Affects linux versions < 5.17.6-1. Fixed in 5.17.6-1. 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 Linux kernel is the core component of many operating systems, providing essential services for hardware and software management. It is known for its stability, performance, and security features. However, like any complex software, it is susceptible to vulnerabilities that can compromise system integrity. The specific vulnerability in question relates to the io_uring subsystem, which facilitates asynchronous I/O operations, enhancing performance in various applications. This vulnerability could potentially allow unauthorized access or manipulation of system resources.

Vulnerability Detail

The vulnerability identified as CVE-2022-49056 arises from improper handling of credential assignments during file operations in the io_uring subsystem. When the system attempts to assign credentials after a file assignment fails, it may lead to inconsistent states, allowing for potential security breaches. This flaw can be exploited by attackers to gain unauthorized access to system resources or escalate privileges, posing significant risks to system security and stability.

How To Fix

Minimum fixed version

5.17.6-1

This is the first release that contains the fix.

sudo apt-get install --only-upgrade linux

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Workaround

Currently, no specific workarounds have been provided for this vulnerability. It is strongly advised to apply the patch as soon as it is available to mitigate any potential risks.

Conclusion

CVE-2022-49056 represents a significant vulnerability in the Linux kernel's io_uring subsystem, which could lead to unauthorized access and privilege escalation. Users are strongly advised to update their systems to the patched version to ensure security and stability. Utilizing tools like Vulert can help monitor and identify vulnerabilities in your software effectively.

See every vulnerability recorded for linux →

Share this vulnerability

FAQ

CVE-2022-49056 is a vulnerability in the Linux kernel's io_uring subsystem that involves improper handling of credential assignments, potentially leading to unauthorized access.

You can use Vulert, which monitors open-source vulnerabilities in your software. By uploading your manifest file, such as package-lock.json, you can check for vulnerabilities without requiring installation.

Exploitation of this vulnerability could allow attackers to gain unauthorized access to system resources or escalate privileges, compromising system security.

Yes, a patch is available in the form of an updated Linux kernel version 5.17.6-1. Users are encouraged to update their systems to this version.

While there are no specific workarounds, it is crucial to prioritize updating your kernel to mitigate risks associated with this vulnerability.

Related vulnerabilities

Recent vulnerabilities recorded for linux.

How To Fix

Minimum fixed version

5.17.6-1

This is the first release that contains the fix.

sudo apt-get install --only-upgrade linux

Tip — Not sure which version your app runs? Vulert can match this fix to it. 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