NFSv4.2: Reference Count Leaks in _nfs42_proc_copy_notify()
Summary
GSD-2022-1001992: NFSv4.2: fix reference count leaks in _nfs42_proc_copy_notify(). Affects Kernel versions < 9b9feec97c1fc7dd9bb69f62c4905cddf1801599. 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 in the Linux ecosystem is responsible for providing the core functionality of the operating system. It includes essential components such as device drivers, process management, memory management, and file system support. The NFSv4.2 protocol is a network file system protocol used for sharing files and directories across a network. The _nfs42_proc_copy_notify() function is a part of the NFSv4.2 implementation in the Kernel package.
Vulnerability Detail
The _nfs42_proc_copy_notify() function in the NFSv4.2 implementation of the Kernel package suffers from reference count leaks. This vulnerability can potentially be exploited by an attacker to cause a denial-of-service condition or execute arbitrary code with elevated privileges. The vulnerability originates from improper handling of reference counts, leading to memory leaks and potential use-after-free scenarios. Successful exploitation of this vulnerability could result in system instability or unauthorized access to sensitive information.
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 known workaround available for this vulnerability. It is advised to apply the official fix by updating the Linux Kernel package.
Conclusion
The NFSv4.2 implementation in the Kernel package suffers from reference count leaks in the _nfs42_proc_copy_notify() function. This vulnerability can lead to a denial-of-service condition or allow an attacker to execute arbitrary code with elevated privileges. It is crucial to update the Linux Kernel package to version v5.10.111 or later to fix this vulnerability. For further support on vulnerability remediation, you can reach out to DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
This vulnerability can potentially lead to a denial-of-service condition or allow an attacker to execute arbitrary code with elevated privileges. It may also result in system instability or unauthorized access to sensitive information.
You can use tools like Vulert Playground (https://vulert.com/scanner) to check if your system is affected by this vulnerability. Vulert Playground allows you to analyze your manifest file, such as package-lock.json, and provides real-time alerts for open-source vulnerabilities.
Yes, a patch for this vulnerability is available in the Linux Kernel version v5.10.111. It is recommended to update the Kernel package to the latest version to apply the fix.
At the time of this report, there are no known public exploits available for this vulnerability. However, it is crucial to apply the fix as soon as possible to mitigate any potential risks.
For more details about this vulnerability, you can refer to the source link provided in the database-specific information section of this report.
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
