watch_queue: Fix NULL dereference in error cleanup

Kernel Updated 02 Oct 2025

Summary

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

GSD-2022-1001580: watch_queue: Fix NULL dereference in error cleanup. Affects Kernel versions >= c73be61cede5882f9605a852414db559c0ebedfd, < 112a2f9b0a8457794095a0450598f150724ec456. 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 package is a fundamental component of the Linux operating system. It provides the core functionality and interfaces for the system's hardware and software components. The watch_queue module is responsible for managing file watches and notifying processes of relevant events. This vulnerability in the watch_queue module can lead to a NULL dereference during error cleanup.

Vulnerability Detail

The vulnerability in the watch_queue module arises from a NULL dereference issue during error cleanup. When certain error conditions occur, the code fails to handle them correctly, resulting in a NULL pointer being dereferenced. This can lead to a system crash or potential privilege escalation if exploited by an attacker. The vulnerability was introduced in version v5.8 of the Linux Kernel and has been fixed in version v5.16.19.

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.16.19 or later. This can be done by obtaining the latest version from the official Linux Kernel repository and following the installation instructions provided. Additionally, it is advisable to regularly update the Kernel to ensure the latest security patches are applied.

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

Workaround

There is no specific workaround mentioned for this vulnerability. The recommended approach is to update the Linux Kernel to the fixed version.

Conclusion

The watch_queue vulnerability in the Linux Kernel can result in a NULL dereference during error cleanup. This can potentially lead to system crashes or privilege escalation. It is crucial to update the Kernel to version v5.16.19 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

The vulnerability can potentially lead to a system crash or privilege escalation if exploited by an attacker.

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 it will provide real-time alerts for open-source vulnerabilities.

At the time of this report, there is no known exploit for this vulnerability. However, it is important to apply the recommended fix to mitigate any potential risks.

Yes, this vulnerability can be remotely exploited if an attacker can gain access to the affected system.

The primary mitigation for this vulnerability is to update the Linux Kernel to the fixed version. Regularly updating the Kernel and implementing other security best practices can also help reduce the risk of exploitation.

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.16.19 or later. This can be done by obtaining the latest version from the official Linux Kernel repository and following the installation instructions provided. Additionally, it is advisable to regularly update the Kernel to ensure the latest security patches are applied.

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.