NFS: Avoid writeback threads getting stuck in mempool_alloc() - Kernel
Summary
GSD-2022-1001025: NFS: Avoid writeback threads getting stuck in mempool_alloc(). Affects Kernel versions < a6caeddd68977a1aaaf62fbd1955b41dd5c3c5d3. 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 critical component of the Linux operating system that provides core functionality and manages system resources. It acts as an interface between the hardware and software layers, facilitating communication and coordination between various components. The NFS (Network File System) is a distributed file system protocol that allows remote file access over a network. It is implemented in the Kernel and enables file sharing between different systems. However, a vulnerability has been discovered in the NFS implementation that can lead to writeback threads getting stuck in mempool_alloc().
Vulnerability Detail
The vulnerability in the NFS implementation can cause writeback threads to become stuck in mempool_alloc(). This can result in resource exhaustion and a denial-of-service (DoS) condition. Attackers may exploit this vulnerability to exhaust system resources, leading to system instability or crashes. The issue has been fixed in Linux Kernel version v5.17.3 by commit a6caeddd68977a1aaaf62fbd1955b41dd5c3c5d3.
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 mentioned for this vulnerability.
Conclusion
The NFS vulnerability in the Kernel can lead to writeback threads getting stuck in mempool_alloc(), resulting in resource exhaustion and a denial-of-service (DoS) condition. It is crucial to update the Linux Kernel to version v5.17.3 or later to mitigate this vulnerability. For further support on vulnerability remediation, you can reach out to DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
The vulnerability can lead to resource exhaustion and a denial-of-service (DoS) condition. It may result in system instability or crashes.
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 and the Vulert Playground will analyze it for any open-source vulnerabilities, including this one.
Yes, the vulnerability has been fixed in Linux Kernel version v5.17.3 by commit a6caeddd68977a1aaaf62fbd1955b41dd5c3c5d3. It is recommended to update to this version or later to mitigate the vulnerability.
Yes, this vulnerability can be exploited remotely if the affected system is accessible over the network.
You can find more information about this vulnerability in the GSD-2022-1001025.json file available in the GSD database (https://github.com/cloudsecurityalliance/gsd-database/blob/main/2022/1001xxx/GSD-2022-1001025.json).
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
