Vulnerability in Kernel: mm/pages_alloc.c
Summary
GSD-2022-1001921: mm/pages_alloc.c: don't create ZONE_MOVABLE beyond the end of a node. Affects Kernel versions >= 2a1e274acf0b1c192face19a4be7c12d4503eaaf, < a74bb0eeabcdbf61e9b5eef36c0cba70ac8f1926. 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 is a critical component of the Linux operating system that manages system resources and facilitates communication between hardware and software. It provides essential functionalities such as memory management, process scheduling, and device drivers. The vulnerability in the mm/pages_alloc.c file affects the Kernel's ability to create ZONE_MOVABLE beyond the end of a node. This vulnerability was introduced in version 2.6.23 and has been fixed in version 5.15.33 of the Linux Kernel.
Vulnerability Detail
The vulnerability in mm/pages_alloc.c allows for the creation of ZONE_MOVABLE beyond the end of a node. While the impact and attack plausibility have not been proven, this vulnerability could potentially lead to memory corruption or privilege escalation attacks. Attackers may exploit this vulnerability to gain unauthorized access to sensitive information or execute arbitrary code on the affected system. It is crucial to apply the necessary fixes to mitigate the risk associated with this vulnerability.
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.
Conclusion
The vulnerability in Kernel's mm/pages_alloc.c file can potentially lead to memory corruption or privilege escalation attacks. It is crucial to update the Linux Kernel to version 5.15.33 or later to mitigate the risk associated with this vulnerability. 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 could potentially lead to memory corruption or privilege escalation attacks. Attackers may exploit this vulnerability to gain unauthorized access to sensitive information or execute arbitrary code on the affected system.
You can use the Vulert Playground at Vulert Scanner to check if your system is affected by this vulnerability. Simply upload your manifest file, such as package-lock.json, and Vulert will analyze it in real-time to identify any open-source vulnerabilities, including this one.
At the time of this report, there is no known exploit for this vulnerability. However, it is crucial to apply the necessary fixes to mitigate the risk associated with this vulnerability.
There are no reported incidents related to this vulnerability at the time of this report. However, it is essential to stay updated with security advisories and apply the necessary patches to ensure the security of your system.
You can find more information about this vulnerability in the official Linux Kernel repository or through security advisories provided by your Linux distribution.
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
