NFSv4: Add an fattr allocation to _nfs4_discover_trunking() in Kernel
Summary
GSD-2022-1004230: NFSv4: Add an fattr allocation to _nfs4_discover_trunking(). Affects Kernel versions >= 6015292653d95ba9f72906e2b65e536aa5807d64, < 2f42531f545f2670192b894d14d50e0539e47e24. 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 is a critical component of the Linux operating system that provides core functionality and acts as a bridge between hardware and software. It manages system resources, facilitates communication between different software components, and enables the execution of user programs. The NFSv4 protocol is used for network file sharing, allowing remote access to files over a network. The _nfs4_discover_trunking() function is responsible for discovering trunking capabilities in NFSv4 servers.
However, a vulnerability has been identified in the Kernel's implementation of _nfs4_discover_trunking().
Vulnerability Detail
The vulnerability in _nfs4_discover_trunking() was introduced in version v5.18.3 of the Linux Kernel and fixed in version v5.18.10. It involves a missing fattr allocation, which could potentially lead to security vulnerabilities. The impact and attack plausibility of this vulnerability have not been proven yet. Further details can be found in the references link provided.
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 mentioned for this vulnerability.
Conclusion
In conclusion, the NFSv4 vulnerability in the Kernel's _nfs4_discover_trunking() function can be fixed by updating to version v5.18.10 or later. It is important to stay updated with the latest security patches to ensure the integrity and security of your system. For further support on vulnerability remediation, you can reach out to DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
The impact of this vulnerability is currently unknown as its attack plausibility has not been proven yet.
You can use Vulert's 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 alert you in real-time if any open-source vulnerabilities, including this one, are detected.
Yes, a patch is available in version v5.18.10 of the Linux Kernel. It is recommended to update to this version or a later one to fix the vulnerability.
No known exploits for this vulnerability have been reported at this time.
You can find more information about this vulnerability in the references link provided.
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.