watch_queue: Fix NULL dereference in error cleanup
Summary
GSD-2022-1001273: watch_queue: Fix NULL dereference in error cleanup. Affects Kernel versions >= c73be61cede5882f9605a852414db559c0ebedfd, < b6f5ad3e45d19f9c4ee3e8a2aff829f28d68591d. No fix is published. How to fix ↓
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.
No signup required · Results in about 60 seconds
Background
The Kernel package is a crucial component of the Linux operating system. It provides the core functionality and acts as an interface between the hardware and software layers. The watch_queue module is responsible for managing file system watches. It allows processes to monitor changes to files and directories. However, a vulnerability has been discovered in the watch_queue module that 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 module fails to handle them properly, resulting in a NULL pointer being dereferenced. This can lead to a system crash or potential privilege escalation for an attacker who can trigger the error condition. The vulnerability was introduced in version v5.8 of the Linux Kernel and has been fixed in version v5.17.2.
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 specific workaround available for this vulnerability. The recommended approach is to apply the fix by updating the Linux Kernel to the patched version.
Conclusion
The watch_queue module in the Linux Kernel is vulnerable to a NULL dereference issue during error cleanup. This can lead to system crashes or potential privilege escalation. It is crucial to update the Linux Kernel to version v5.17.2 or later to mitigate this vulnerability. For further support and assistance in vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
The vulnerability can lead to a system crash or potential privilege escalation for an attacker who can trigger the error condition.
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 the playground will analyze it for any open-source vulnerabilities, including this one.
At the time of this report, there is no known exploit for this vulnerability. However, it is important to apply the fix as soon as possible to mitigate any potential risks.
No, this vulnerability requires an attacker to have local access to the system in order to trigger the error condition and potentially exploit it.
The fix for this vulnerability is specific to the Linux Kernel. It is recommended to follow the official documentation and guidelines provided by the Linux Kernel community for updating the Kernel.
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
