Fix hardlockup on vmap stack overflow in Kernel
Summary
GSD-2021-1002468: powerpc/32: Fix hardlockup on vmap stack overflow. Affects Kernel versions >= c118c7303ad528be8ff2aea8cd1ee15452c763f0, < dfe906da9a1abebdebe8b15bb3e66a2578f6c4c7. 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 provides core functionalities and interfaces between hardware and software. It manages system resources, including memory, processes, and device drivers. The vulnerability in question affects the powerpc/32 architecture of the Kernel. The powerpc/32 architecture is used in 32-bit PowerPC processors. The vulnerability can lead to a hardlockup when there is a stack overflow in the vmap function.
Vulnerability Detail
The vulnerability arises from a stack overflow in the vmap function in the powerpc/32 architecture of the Kernel. When the stack overflows, it can cause a hardlockup, resulting in the system becoming unresponsive. The impact of this vulnerability can range from denial of service to potential security risks if an attacker can trigger the stack overflow. The vulnerability was introduced in version v5.10 of the Kernel and has been fixed in version v5.10.83.
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 the powerpc/32 architecture of the Kernel, which causes a hardlockup on vmap stack overflow, has been addressed in version v5.10.83. It is recommended to update the Kernel to this version or later to mitigate the vulnerability. For further support on vulnerability remediation, you can reach out to DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
The impact can range from denial of service to potential security risks if an attacker can trigger the stack overflow.
The vulnerability was introduced in version v5.10 of the Kernel.
You can use Vulert's playground at Vulert Scanner to check if your system is affected by this vulnerability.
Yes, the vulnerability has been fixed in version v5.10.83 of the Kernel.
You can update the Kernel by following the standard procedures for updating the Linux Kernel on your specific distribution.
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
