watch_queue: Free the page array when watch_queue is dismantled in Kernel
Summary
GSD-2022-1001431: watch_queue: Free the page array when watch_queue is dismantled. Affects Kernel versions >= c73be61cede5882f9605a852414db559c0ebedfd, < 3963a5d1ff75585bddf0c3a918566a6be09d7520. 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 is a crucial component of the Linux operating system that acts as a bridge between the hardware and software layers. It provides essential services and manages system resources. The watch_queue is a data structure used in the Kernel to track page watches. It maintains an array of pages that are being monitored for changes. However, a vulnerability has been discovered in the watch_queue implementation that can lead to memory leaks and potential security risks.
Vulnerability Detail
The vulnerability in the watch_queue arises from a failure to free the page array when the watch_queue is dismantled. This can result in memory leaks, where allocated memory is not properly released, leading to resource exhaustion and potential denial-of-service attacks. An attacker could exploit this vulnerability to exhaust system resources, causing instability or crashes. 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.
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 provided for this vulnerability. The recommended solution is to update the Linux Kernel to the fixed version.
Conclusion
The watch_queue vulnerability in the Linux Kernel can lead to memory leaks and potential denial-of-service attacks. It is crucial to update the Kernel to version v5.16.19 or later to fix this issue. Failure to address this vulnerability may result in resource exhaustion and system instability. For further support on vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
The vulnerability can lead to memory leaks and potential denial-of-service attacks by exhausting system resources.
You can use the Vulert Playground (https://vulert.com/scanner) to check if your system is affected by this vulnerability. Simply upload your package-lock.json file to the playground, and it will alert you if the vulnerability is present.
At the time of this report, there is no known exploit for this vulnerability. However, it is important to update the Kernel to the fixed version to mitigate any potential risks.
No, this vulnerability requires local access to the system. However, it is still important to address the issue to prevent potential attacks from within the system.
This vulnerability specifically affects the Linux Kernel. However, it is always recommended to keep all software and dependencies up to date to ensure overall system security.
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
