Vulnerability in powerpc/idle Package: Corrupting Back Chain When Going Idle
Summary
GSD-2021-1002109: powerpc/idle: Don't corrupt back chain when going idle. Affects Kernel versions >= 6d077c37c4643394b1bae9682da48164fc147ea8, < 65ede7bd97138435c07de602efc8812c586a1d38. 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, which is responsible for managing the idle state of powerpc processors. It provides functionality to put the processor into a low-power state when it is not actively executing tasks. The package is crucial for power management and energy efficiency in powerpc-based systems.
Vulnerability Detail
The vulnerability in the powerpc/idle package allows for the corruption of the back chain when the processor goes idle. This issue was introduced in version v5.14.15 of the Linux Kernel and was fixed in version v5.14.15. When the back chain is corrupted, it can lead to various security risks and system instability. The impact and attack plausibility of this vulnerability have not been proven yet.
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 powerpc/idle package in the Linux Kernel is vulnerable to back chain corruption when the processor goes idle. It is recommended to update the kernel to version v5.14.15 or later to fix this vulnerability. For further support on vulnerability remediation, you can contact DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
The powerpc/idle package is a component of the Linux Kernel that manages the idle state of powerpc processors.
The corruption of the back chain can lead to security risks and system instability.
You can use Vulert's playground at Vulert Scanner to check if your system is affected by this vulnerability. Vulert uses a manifest file like package-lock.json to monitor and alert in real-time for open-source vulnerabilities.
Yes, the vulnerability has been fixed in version v5.14.15 of the Linux Kernel.
You can find more information about this vulnerability in the Open Source Vulnerability database at https://github.com/cloudsecurityalliance/gsd-database/blob/main/2021/1002xxx/GSD-2021-1002109.json
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
