Vulnerability in Kernel package: Fix kfree() of bootmem memory again
Summary
GSD-2022-1001820: kernel/resource: fix kfree() of bootmem memory again. Affects Kernel versions >= ebff7d8f270d045338d9f4796014f4db429a17f9, < a9e88c2618d228d7a4e7e515cf30dc0d0d813f27. 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 package is a crucial component of the Linux operating system. It provides the core functionality and acts as an interface between the hardware and software layers. The package manages system resources, including memory allocation and deallocation. One of the key features of the Kernel package is the bootmem memory management mechanism, which handles memory allocation during the boot process. However, a vulnerability has been identified in the kfree() function of the bootmem memory management, which can lead to potential security issues.
Vulnerability Detail
The vulnerability in the Kernel package affects the kfree() function of the bootmem memory management. When freeing memory using kfree(), there is a flaw that can result in freeing bootmem memory incorrectly. This can lead to various security risks, including memory corruption, information disclosure, and potential privilege escalation. The vulnerability was introduced in version v3.10 of the Linux Kernel and has been fixed in version v5.15.33.
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 vulnerability in the Kernel package, specifically in the kfree() function of the bootmem memory management, can lead to memory corruption, information disclosure, and potential privilege escalation. It is crucial to update the Linux Kernel package to version v5.15.33 or later to mitigate this vulnerability. For further support on vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
The vulnerability can potentially lead to memory corruption, information disclosure, and privilege escalation.
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 provide real-time alerts for open-source vulnerabilities.
No specific workaround has been mentioned for this vulnerability. It is recommended to update to the fixed version of the Linux Kernel package.
The vulnerability was introduced in version v3.10 of the Linux Kernel and has been fixed in version v5.15.33.
You can find more information about this vulnerability in the Open Source Vulnerability Database (OSVDB) entry with ID GSD-2022-1001820.
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
