Vulnerability in Kernel package: ipmi: fix initialization when workqueue allocation fails
Summary
GSD-2021-1002805: ipmi: fix initialization when workqueue allocation fails. Affects Kernel versions >= f717f29e84688b0327ae6e51fabaf397fbcd18d3, < 8b745616ba8f2db389a59e5678fdbe28ad5883bf. 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 package is a fundamental component of the Linux operating system, responsible for managing the system's core functionality. It provides essential services and interfaces for hardware, software, and user interactions. The ipmi module within the Kernel package enables Intelligent Platform Management Interface (IPMI) functionality, allowing remote management and monitoring of computer systems. This vulnerability specifically affects the initialization process of the ipmi module when workqueue allocation fails.
Vulnerability Detail
The vulnerability arises from a flaw in the initialization mechanism of the ipmi module. When the allocation of a workqueue fails, the module fails to handle this situation properly, leading to potential security issues. Although the impact and attack plausibility have not been proven, this vulnerability could potentially be exploited by malicious actors to gain unauthorized access, execute arbitrary code, or cause a denial-of-service condition. The vulnerability was introduced in version v5.10.84 of the Linux Kernel and has been fixed in version v5.10.89.
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 Kernel package's ipmi module is vulnerable to an issue in its initialization process when workqueue allocation fails. This vulnerability could potentially lead to unauthorized access, arbitrary code execution, or denial-of-service. It is crucial to update the Kernel package to version v5.10.89 or later to mitigate this vulnerability. For further support and assistance in vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
The impact of this vulnerability is not yet proven, but it could potentially allow unauthorized access, arbitrary code execution, or cause a denial-of-service condition.
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 to the playground, and it will provide real-time alerts for open-source vulnerabilities.
No specific workaround has been provided for this vulnerability. It is recommended to update the Kernel package to the fixed version.
Yes, this vulnerability can potentially be exploited remotely if the affected system is exposed to the network.
There are no known instances of this vulnerability being exploited in the wild at the time of this report.
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
