Memory Leak Vulnerability in nfs Package
Summary
GSD-2021-1001326: nfs: fix acl memory leak of posix_acl_create(). Affects Kernel versions >= 013cdf1088d7235da9477a2375654921d9b9ba9f, < d0b32dc1409f7e65e4fcc34e236462268e69a357. 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 nfs package is a component of the Linux Kernel, which is responsible for providing network file system support. It allows remote file systems to be mounted and accessed over a network. The package includes various functions and modules for handling file operations, including the management of access control lists (ACLs).
Vulnerability Detail
The identified vulnerability in the nfs package is a memory leak issue within the posix_acl_create() function. This function is responsible for creating access control lists for files and directories. Due to a coding error, the function fails to release allocated memory when an ACL is created, leading to a memory leak. An attacker could potentially exploit this vulnerability by repeatedly creating ACLs, causing memory exhaustion and potentially leading to a denial of service (DoS) condition. The vulnerability was introduced in version v3.14 of the Linux Kernel and has been fixed in version v5.4.134.
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 →
Conclusion
The memory leak vulnerability in the nfs package can lead to memory exhaustion and a denial of service (DoS) condition. To mitigate this issue, it is crucial to update the Linux Kernel to version v5.4.134 or later. For further support and assistance in vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
The vulnerability can lead to a memory leak, potentially causing memory exhaustion and a denial of service (DoS) condition.
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.
No specific workaround has been provided for this vulnerability. It is recommended to update the Linux Kernel to the fixed version.
No, this vulnerability does not have a remote exploitation vector. An attacker would need local access to the system to exploit the memory leak issue.
There is no information available regarding active exploitation of this vulnerability in the wild.
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.
