Mismatch between reconstructed freelist depth and cnt in mm, slub
Summary
GSD-2021-1002179: mm, slub: fix mismatch between reconstructed freelist depth and cnt. Affects Kernel versions >= c3895391df385c6628638f014c87e16f5e2efd45, < 899447f669da76cc3605665e1a95ee877bc464cc. 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 vulnerability affects the Kernel package in the Linux ecosystem. The Kernel is the core component of the operating system that manages system resources and provides an interface for software to interact with hardware. The specific vulnerability is related to the mm (memory management) subsystem and the slub allocator. The slub allocator is responsible for managing kernel memory allocations. The vulnerability arises from a mismatch between the reconstructed freelist depth and the cnt (count) value, leading to potential memory corruption and security issues.
Vulnerability Detail
The vulnerability in the mm, slub subsystem of the Kernel package can result in memory corruption and potential security risks. It occurs due to a mismatch between the reconstructed freelist depth and the cnt value. This mismatch can be exploited by an attacker to manipulate memory allocations and potentially execute arbitrary code or cause a denial-of-service condition. The vulnerability was introduced in version v4.17 of the Linux Kernel and has been fixed in version v5.15 by commit 899447f669da76cc3605665e1a95ee877bc464cc.
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 approach is to apply the fix by updating the Kernel to the latest version.
Conclusion
The vulnerability in the mm, slub subsystem of the Kernel package can lead to memory corruption and potential security risks. It is crucial to update the Kernel to version v5.15 or later to mitigate these risks. For further support on vulnerability remediation, you can reach out to DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
The vulnerability can lead to memory corruption and potential security risks. It may allow an attacker to manipulate memory allocations and potentially execute arbitrary code or cause a denial-of-service 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 provide real-time monitoring and alerts for open-source vulnerabilities, including this one.
There is no information available regarding exploitation of this vulnerability in the wild. However, it is recommended to apply the fix as soon as possible to mitigate any potential risks.
The primary mitigation is to update the Kernel package to version v5.15 or later. This will include the fix for the vulnerability. Additionally, it is recommended to follow security best practices, such as keeping the system up to date with the latest patches and using proper access controls.
You can find more information about this vulnerability in the GSD-2021-1002179 entry of the GSD database maintained by the Cloud Security Alliance. The entry provides additional details, including the commit history and affected versions.
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
