Refcount Leak in icp_opal_init() in powerpc/xics
Summary
GSD-2022-1002699: powerpc/xics: fix refcount leak in icp_opal_init(). Affects Kernel versions < 9a42bc2494fadb453de00ce61042e588563ddc6d. 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/xics package is a component of the Linux Kernel, which is responsible for handling interrupt controllers on PowerPC systems. The icp_opal_init() function in this package initializes the interrupt controller for OpenPower Abstraction Layer (OPAL) systems. It manages the reference count for the interrupt controller, ensuring proper initialization and cleanup. However, a vulnerability has been discovered in this function that leads to a refcount leak.
Vulnerability Detail
The refcount leak vulnerability in icp_opal_init() occurs when the function fails to properly release the reference count on the interrupt controller in certain error scenarios. This can result in a resource leak, leading to potential memory corruption or denial of service. An attacker may be able to exploit this vulnerability to cause a system crash or execute arbitrary code with elevated privileges. The vulnerability has been assigned the ID GSD-2022-1002699 and has been fixed in Linux Kernel version v5.18.3.
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
In conclusion, the refcount leak vulnerability in icp_opal_init() in the powerpc/xics package of the Linux Kernel can lead to resource leaks and potential memory corruption or denial of service. It is crucial to update to Linux Kernel version v5.18.3 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 lead to a resource leak, potentially resulting in memory corruption or denial of service. An attacker may be able to crash the system or execute arbitrary code with elevated privileges.
You can use the Vulert 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 monitoring and alerts for open-source vulnerabilities.
Yes, this vulnerability has been fixed in Linux Kernel version v5.18.3 by commit 9a42bc2494fadb453de00ce61042e588563ddc6d.
No, there are no known workarounds for this vulnerability. It is recommended to update to the fixed version of the Linux Kernel.
You can find more information about this vulnerability in the GSD database entry at https://github.com/cloudsecurityalliance/gsd-database/blob/main/2022/1002xxx/GSD-2022-1002699.json.
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.