Vulnerability in powerpc/perf Package: power_pmu_disable Function
Summary
GSD-2022-1000263: powerpc/perf: Fix power_pmu_disable to call clear_pmi_irq_pending only if PMI is pending. Affects Kernel versions >= fadcafa3959281ce2d96feedece8c75c3f95f8a5, < 28aaed966e76807a71de79dd40a8eee9042374dd. 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/perf package is a component of the Linux Kernel, which is responsible for performance monitoring on PowerPC architectures. It provides tools and functionality for monitoring and analyzing system performance. The power_pmu_disable function is a part of this package and is used to disable the PowerPC Performance Monitor Unit (PMU).
Vulnerability Detail
The power_pmu_disable function in the powerpc/perf package does not correctly handle the clearing of pending Performance Monitor Interrupts (PMIs). This can lead to a situation where the PMI interrupt remains pending even after the PMU is disabled. An attacker could potentially exploit this vulnerability to trigger a malicious PMI interrupt and execute arbitrary code with elevated privileges.
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 known workaround for this vulnerability. It is necessary to update the Linux Kernel to the fixed version.
Conclusion
The powerpc/perf package in the Linux Kernel is vulnerable to a flaw in the power_pmu_disable function, which can be exploited to execute arbitrary code with elevated privileges. It is crucial to update the Linux Kernel to version v5.15.19 or later to fix this vulnerability. If you are unsure whether your system is affected, you can use the Vulert Playground to check for the presence of the vulnerability. For additional support, please contact DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
This vulnerability could allow an attacker to execute arbitrary code with elevated privileges on systems running the affected version of the Linux Kernel.
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 analyze and alert you if the vulnerability is present.
There are no known public exploits for this vulnerability at the time of this report. However, it is important to update your system to the fixed version to mitigate the risk.
No, this vulnerability requires local access to the system in order to exploit it.
For further support on vulnerability remediation, you can contact info@devnack.com.
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
