Vulnerability in powerpc/idle Package: Corrupting Back Chain when Going Idle
Summary
UVI-2021-1002047: powerpc/idle: Don't corrupt back chain when going idle. Affects Kernel versions >= fbd724c49bead048ae9fc1a5b7bff2fb3e54f855, < c5c2a80368e97ac179d6a101c99f1e1f36146ec2. 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 powerpc/idle package is a component of the Linux Kernel, specifically designed for powerpc architecture. It provides functionality for managing the idle state of powerpc processors. The package is responsible for transitioning the processor to an idle state when it is not actively executing tasks, thereby conserving power. However, a vulnerability has been discovered in this package that can lead to the corruption of the back chain when the processor goes idle.
Vulnerability Detail
The vulnerability in the powerpc/idle package occurs when the processor transitions to the idle state. Due to a coding error, the back chain, which is a critical data structure used for maintaining the execution context, can be corrupted. This corruption can potentially lead to various issues, including system crashes, data corruption, and privilege escalation attacks. The vulnerability has been assigned the ID UVI-2021-1002047 and has been fixed in Linux Kernel version v5.10.76.
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 Linux Kernel.
Conclusion
The vulnerability in the powerpc/idle package can result in the corruption of the back chain when the processor goes idle. This can lead to system crashes, data corruption, and potential privilege escalation attacks. It is crucial to update the Linux Kernel to version v5.10.76 or later to fix this vulnerability. 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 system crashes, data corruption, and potential privilege escalation attacks.
You can use the Vulert Playground (https://vulert.com/scanner) to check if your system is affected by this vulnerability. Simply upload your package-lock.json file and the Vulert Playground will analyze it for any open-source vulnerabilities, including this one.
At the time of this report, there is no known exploit for this vulnerability. However, it is important to apply the fix as soon as possible to mitigate any potential risks.
The fix requires updating the Linux Kernel to version v5.10.76 or later. It is recommended to ensure compatibility with the target system before applying the update.
You can refer to the vulnerability details in the Open Source Vulnerability format provided by the Cloud Security Alliance's GSD database. The details can be found at: https://github.com/cloudsecurityalliance/gsd-database/blob/main/2021/1002xxx/UVI-2021-1002047.json
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.