Vulnerability in Kernel: io-wq: drop wqe lock before creating new worker

Kernel Updated 02 Oct 2025

Summary

27/12/2021
N/A
No i
Unrated
Not published

GSD-2021-1002761: io-wq: drop wqe lock before creating new worker. Affects Kernel versions >= 4b4e5bbf9386d4ec21d91c0cb0fd60b9bba778ec, < 11053a021937aa403c883d3e8ef78d8c5308f583. 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 manages communication between hardware and software. It provides essential functions and services to enable the proper functioning of the system. The io-wq module within the Kernel is responsible for handling input/output workqueues. Workqueues are used to schedule and execute tasks asynchronously. The vulnerability in question arises when the wqe lock is not released before creating a new worker. This can lead to potential security issues.

Vulnerability Detail

The vulnerability occurs in the io-wq module of the Kernel. When creating a new worker, the wqe lock is not dropped, which can result in security vulnerabilities. The exact impact and attack vectors are yet to be proven, but it is crucial to address this issue to prevent potential exploitation. The vulnerability was introduced in version v5.15.11 of the Linux Kernel by commit 4b4e5bbf9386d4ec21d91c0cb0fd60b9bba778ec. It has been fixed in version v5.15.11 by commit 11053a021937aa403c883d3e8ef78d8c5308f583.

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.15.11 or later. This update includes the necessary fix committed in commit 11053a021937aa403c883d3e8ef78d8c5308f583. Updating the Kernel will ensure that the wqe lock is properly dropped before creating a new worker, mitigating the security risk.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Conclusion

In conclusion, the vulnerability in the Kernel's io-wq module can lead to potential security issues. It is recommended to update the Linux Kernel to version v5.15.11 or later to address this vulnerability. For further support on vulnerability remediation, you can reach out to DevNack.com.

See every vulnerability recorded for Kernel →

Share this vulnerability

FAQ

The exact impact of this vulnerability is yet to be proven. However, it has the potential to be exploited by malicious actors to gain unauthorized access or perform other malicious activities.

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 Vulert will analyze it in real-time to identify any open-source vulnerabilities, including this one.

At the moment, there are no known workarounds for this vulnerability. It is recommended to update the Linux Kernel to the fixed version as soon as possible.

There is no evidence to suggest that this vulnerability is actively being exploited at this time. However, it is crucial to apply the fix to prevent any potential exploitation.

You can find more information about this vulnerability in the GSD-2021-1002761 entry of the GSD database maintained by the Cloud Security Alliance. The link to the entry is available at https://github.com/cloudsecurityalliance/gsd-database/blob/main/2021/1002xxx/GSD-2021-1002761.json.

Related vulnerabilities

Recent vulnerabilities recorded for Kernel.

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.15.11 or later. This update includes the necessary fix committed in commit 11053a021937aa403c883d3e8ef78d8c5308f583. Updating the Kernel will ensure that the wqe lock is properly dropped before creating a new worker, mitigating the security risk.

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

Follow Vulert in Google

Get more Vulert vulnerability and dependency-security updates in Google Search and AI results.