NFS: Corrupting the value of pg_bytes_written in nfs_do_recoalesce()
Summary
GSD-2021-1000692: NFS: Don't corrupt the value of pg_bytes_written in nfs_do_recoalesce(). Affects Kernel versions >= a7d42ddb3099727f58366fa006f850a219cce6c8, < b291baae24f876acd5a5dd57d0bb2bbac8a68b0c. 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 fundamental component of the Linux operating system. It provides the core functionality and interfaces for the system's hardware and software components. The NFS (Network File System) is a distributed file system protocol that allows remote file access over a network. The nfs_do_recoalesce() function is responsible for reassembling fragmented data in NFS. However, a vulnerability exists in this function that can corrupt the value of pg_bytes_written.
Vulnerability Detail
The vulnerability in nfs_do_recoalesce() can lead to the corruption of the pg_bytes_written value. This can have various consequences, including data integrity issues, potential data loss, and system instability. The vulnerability was introduced in version v4.0 of the Linux Kernel and has been fixed in version v4.9.271. The impact and attack plausibility of this vulnerability have not been proven yet.
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 vulnerability in nfs_do_recoalesce() can lead to the corruption of the pg_bytes_written value in the NFS component of the Linux Kernel. It is crucial to update the Kernel package to version v4.9.271 or later to mitigate the risk. For further support on vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
The vulnerability can lead to data corruption, potential data loss, and system instability.
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 to the playground and it will analyze and alert you if the vulnerability is present.
There is no known exploit for this vulnerability at the moment. However, it is important to apply the necessary updates to mitigate the risk.
No, only versions starting from v4.0 up to v4.9.270 are affected. The vulnerability has been fixed in version v4.9.271.
The remote exploitability of this vulnerability has not been proven yet. However, it is recommended to apply the necessary updates to ensure system security.
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
