Mismatch between reconstructed freelist depth and cnt in mm, slub
Summary
GSD-2021-1001982: mm, slub: fix mismatch between reconstructed freelist depth and cnt. Affects Kernel versions >= c3895391df385c6628638f014c87e16f5e2efd45, < 21e23e4c02fc9aa1f4b037f30e47d215d1a27f21. 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 due to a mismatch between the reconstructed freelist depth and the cnt value. This mismatch can lead to memory corruption and potential security vulnerabilities.
Vulnerability Detail
The vulnerability originates from a mismatch between the reconstructed freelist depth and the cnt value in the slub allocator. This mismatch can occur when the freelist is reconstructed during memory allocation. If an attacker can trigger this vulnerability, they may be able to corrupt memory and potentially execute arbitrary code with kernel privileges. The impact of this vulnerability can range from denial of service to privilege escalation attacks. The vulnerability was introduced in version v4.17 of the Linux Kernel and has been fixed in version v4.19.214.
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 update the Linux Kernel to the fixed version.
Conclusion
The vulnerability in the mm, slub allocator in the Linux Kernel can lead to memory corruption and potential security vulnerabilities. It is crucial to update the Kernel to the fixed version to mitigate the risk. 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 can range from denial of service to privilege escalation attacks. An attacker may be able to corrupt memory and potentially execute arbitrary code with kernel privileges.
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 in real-time.
There is no specific workaround mentioned for this vulnerability. It is recommended to update the Linux Kernel to the fixed version.
This vulnerability was introduced in version v4.17 of the Linux Kernel.
Yes, this vulnerability has been fixed in version v4.19.214 of the Linux Kernel.
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
