NFS: Corruption of pg_bytes_written in nfs_do_recoalesce()
Summary
GSD-2021-1000705: NFS: Don't corrupt the value of pg_bytes_written in nfs_do_recoalesce(). Affects Kernel versions >= a7d42ddb3099727f58366fa006f850a219cce6c8, < e8b8418ce14ae66ee55179901edd12191ab06a9e. 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 NFS (Network File System) is a distributed file system protocol that allows remote file access over a network. It is implemented within the Kernel package and is widely used for sharing files between systems. However, a vulnerability has been identified in the NFS module that can lead to the corruption of the pg_bytes_written value in the nfs_do_recoalesce() function.
Vulnerability Detail
The vulnerability arises from a flaw in the nfs_do_recoalesce() function, which is responsible for handling data coalescing in NFS. By exploiting this vulnerability, an attacker can corrupt the value of pg_bytes_written, potentially leading to data corruption or loss. 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 has been fixed in version v4.4.271.
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 package can result in the corruption of the pg_bytes_written value, potentially leading to data corruption or loss. It is crucial to update the Linux Kernel package to version v4.4.271 or later to mitigate this vulnerability. For further support on vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
The impact of this vulnerability can potentially lead to data corruption or loss.
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 tool will provide real-time alerts for open-source vulnerabilities.
No known exploit for this vulnerability has been reported at this time.
The remote exploitation of this vulnerability has not been proven yet.
The recommended mitigation is to update the Linux Kernel package to the fixed version v4.4.271 or later.
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
