Memory Leak Vulnerability in mm, slub Package
Summary
GSD-2021-1001873: mm, slub: fix potential memoryleak in kmem_cache_open(). Affects Kernel versions >= 210e7a43fa905bccafa9bb5966fba1d71f33eb8b, < 42b81946e3ac9ea0372ba16e05160dc11e02694f. 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 mm, slub package is a component of the Linux Kernel, which is responsible for managing memory allocation and deallocation. It provides a memory management subsystem called SLUB (Simplified Low Overhead Bounded) allocator. The SLUB allocator is used to efficiently allocate and free memory objects in the kernel. However, a vulnerability has been discovered in the kmem_cache_open() function of the mm, slub package, which can lead to potential memory leaks.
Vulnerability Detail
The vulnerability in the kmem_cache_open() function of the mm, slub package can result in memory leaks. When a cache is created using kmem_cache_open(), and an error occurs during the initialization process, the function fails to properly clean up the allocated memory, leading to memory leaks. An attacker could potentially exploit this vulnerability to exhaust system memory resources, causing denial-of-service conditions or other adverse effects.
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. The recommended solution is to update the Linux Kernel to the fixed version.
Conclusion
The memory leak vulnerability in the mm, slub package of the Linux Kernel can lead to memory leaks and potential system instability. It is crucial to update the Linux Kernel to version v5.14.15 or later to mitigate this vulnerability. Regularly updating the kernel is essential to ensure the latest security patches and fixes are applied. For further support on vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
This vulnerability can lead to memory leaks, potentially causing system instability, resource exhaustion, or denial-of-service conditions.
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, and Vulert will analyze it for any open-source vulnerabilities, including this one.
As of now, there is no known exploit for this vulnerability. However, it is important to apply the fix as soon as possible to mitigate any potential risks.
No, only versions starting from v4.8 up to v5.14.14 are affected. The vulnerability was introduced in v4.8 and fixed in v5.14.15.
No, this vulnerability requires local access to the system. It cannot be exploited remotely over a network.
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
