NFSv4.2 Reference Count Leaks in _nfs42_proc_copy_notify()
Summary
GSD-2022-1001703: NFSv4.2: fix reference count leaks in _nfs42_proc_copy_notify(). Affects Kernel versions < b37f482ba9f0e6382c188e3fccf6c4b2fdc938eb. 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
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
Background
The Kernel package is a critical component of the Linux operating system, responsible for managing system resources and facilitating communication between hardware and software. It provides essential functionalities such as process management, memory management, and device drivers. NFSv4.2 is a network file system protocol that allows remote file access and sharing over a network. It is implemented within the Kernel package and is susceptible to reference count leaks in the _nfs42_proc_copy_notify() function.
Vulnerability Detail
The vulnerability in NFSv4.2 arises from reference count leaks in the _nfs42_proc_copy_notify() function. This can lead to memory leaks and potential resource exhaustion. An attacker could potentially exploit this vulnerability to cause denial of service (DoS) attacks or escalate privileges. The impact and attack plausibility of this vulnerability have not been fully proven.
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 NFSv4.2 reference count leaks in _nfs42_proc_copy_notify() vulnerability poses a potential risk of memory leaks, resource exhaustion, and possible privilege escalation. It is crucial to update the Linux Kernel package to version v5.15.34 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 could range from memory leaks to potential resource exhaustion. It could also be exploited by attackers to cause denial of service (DoS) attacks or escalate privileges.
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 provide real-time monitoring and alerts for open-source vulnerabilities.
Yes, a patch is available for this vulnerability in the Linux Kernel version v5.15.34. Updating to this version or a later version will address the vulnerability.
Yes, this vulnerability can be exploited remotely if an attacker can access the affected system over the network.
There are no known instances of this vulnerability being exploited at the time of this report.
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
