NFS: Fix an Oopsable condition in __nfs_pageio_add_request()
Summary
GSD-2021-1000602: NFS: Fix an Oopsable condition in __nfs_pageio_add_request(). Affects Kernel versions >= a7d42ddb3099727f58366fa006f850a219cce6c8, < ee21cd3aa8548e0cbc8c67a80b62113aedd2d101. 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 critical component of the Linux operating system. It provides the core functionality and interfaces for the system, including managing processes, memory, and hardware devices. The NFS (Network File System) is a distributed file system protocol that allows remote file access over a network. It is commonly used for sharing files between systems. The __nfs_pageio_add_request() function is responsible for adding a request to the NFS page I/O subsystem. This vulnerability affects the Linux Kernel and specifically impacts the __nfs_pageio_add_request() function.
Vulnerability Detail
The vulnerability in __nfs_pageio_add_request() can lead to an Oopsable condition. An Oopsable condition refers to a situation where the kernel encounters an unexpected error or state that causes it to panic or crash. This vulnerability can be triggered by a specific sequence of operations or inputs, potentially leading to a denial of service (DoS) or privilege escalation. The impact and attack plausibility of this vulnerability have not been proven yet. The vulnerability was introduced in version v4.0 of the Linux Kernel and is fixed in version v5.10.42.
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
No workaround has been provided for this vulnerability.
Conclusion
The NFS vulnerability in __nfs_pageio_add_request() can lead to an Oopsable condition in the Linux Kernel. While the impact and attack plausibility have not been proven, it is important to stay updated with the latest Kernel version (v5.10.42 or later) to mitigate potential risks. For further support on vulnerability remediation, you can contact DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
The impact of this vulnerability is currently unknown. It may lead to a denial of service (DoS) or privilege escalation.
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 Vulert will analyze it for potential vulnerabilities.
Yes, a patch is available in version v5.10.42 of the Linux Kernel. It is recommended to update to this version or later to fix the vulnerability.
The remote exploitability of this vulnerability has not been determined yet. Further analysis is required to assess the potential for remote exploitation.
There are no known instances of this vulnerability being exploited in the wild. However, it is always recommended to apply security patches and updates to mitigate potential risks.
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
