tipc: wait and exit until all work queues are done

Kernel Updated 02 Oct 2025

Summary

04/06/2021
N/A
No i
Unrated
Not published

GSD-2021-1000598: tipc: wait and exit until all work queues are done. Affects Kernel versions >= d0f91938bede204a343473792529e0db7d599836, < 5195ec5e365a2a9331bfeb585b613a6e94f98dba. 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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The Kernel is a critical component of the Linux operating system that manages system resources and facilitates communication between hardware and software. It provides essential functions such as process management, memory management, and device drivers. The vulnerability in question affects the tipc module, which is responsible for providing transparent inter-process communication between nodes in a cluster. This vulnerability allows an attacker to exploit a race condition in the tipc module, potentially leading to a denial of service or privilege escalation.

Vulnerability Detail

The vulnerability arises from a lack of proper synchronization in the tipc module's work queues. When a process exits, it may leave pending work items in the queues, which can cause resource leaks and instability. An attacker can exploit this by repeatedly creating and terminating processes, exhausting system resources and potentially crashing the system. Additionally, if the attacker can control the work items left in the queues, they may be able to execute arbitrary code with elevated privileges.

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

If updating the Linux Kernel is not immediately feasible, a possible workaround is to limit the number of processes that can be created within a certain time frame. This can help mitigate the impact of the vulnerability by reducing the likelihood of resource exhaustion. However, this workaround may have implications for system performance and should be carefully evaluated before implementation.

Conclusion

The tipc vulnerability in the Linux Kernel can have serious consequences, including resource leaks, system instability, denial of service, and privilege escalation. It is crucial to update the Kernel to the latest version (v5.10.42 or later) to mitigate the risk. If immediate updating is not possible, limiting the number of processes created within a time frame can serve as a temporary workaround. For further assistance and support in addressing this vulnerability, please contact DevNack.com.

See every vulnerability recorded for Kernel →

Share this vulnerability

FAQ

The vulnerability can lead to resource leaks, system instability, denial of service, or privilege escalation.

An attacker can exploit the vulnerability by repeatedly creating and terminating processes, exhausting system resources and potentially crashing the system. They may also be able to execute arbitrary code with elevated privileges if they can control the work items left in the queues.

Yes, the vulnerability is fixed in Linux Kernel version v5.10.42 or later. Users should update their Kernel to the latest version to mitigate the risk.

A possible workaround is to limit the number of processes that can be created within a certain time frame. However, this may impact system performance and should be carefully evaluated.

For more details about this vulnerability, you can refer to the official Linux Kernel repository and the associated commit (5195ec5e365a2a9331bfeb585b613a6e94f98dba).

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