ACPI: CPPC: Avoid out of bounds access when parsing _CPC data in Kernel
Summary
GSD-2022-1001100: ACPI: CPPC: Avoid out of bounds access when parsing _CPC data. Affects Kernel versions >= 337aadff8e4567e39669e07d9a88b789d78458b5, < d7339f2a3938fb56b5f28d53f5345900b5fa0e74. 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 is a fundamental component of the Linux operating system that acts as a bridge between the hardware and software layers. It provides essential services and manages system resources. The ACPI (Advanced Configuration and Power Interface) subsystem within the Kernel handles power management and device configuration. The CPPC (Collaborative Processor Performance Control) mechanism is used to optimize CPU performance. However, a vulnerability exists in the Kernel's ACPI CPPC implementation that can lead to out of bounds access when parsing _CPC (Collaborative Processor Control) data.
Vulnerability Detail
The vulnerability in the ACPI CPPC implementation allows for out of bounds access when parsing _CPC data. This can potentially be exploited by an attacker to gain unauthorized access, execute arbitrary code, or cause a denial of service. The vulnerability was introduced in Kernel version v4.4 and has been fixed in version v5.17.2. The impact and attack plausibility of this vulnerability have not yet been proven.
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 ACPI CPPC vulnerability in the Kernel can lead to out of bounds access when parsing _CPC data. It is recommended to update the Kernel to version v5.17.2 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 impact of this vulnerability is not yet proven, but it could potentially allow an attacker to gain unauthorized access, execute arbitrary code, or cause a denial of service.
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.
Yes, a patch is available in Kernel version v5.17.2. It is recommended to update to this version or later to fix the vulnerability.
Updating the Kernel to the fixed version is the recommended approach to mitigate the risk. However, if updating is not feasible, you can consider implementing additional security measures such as network segmentation, access controls, and intrusion detection systems.
You can find more information about this vulnerability in the GSD database maintained by the Cloud Security Alliance. The specific vulnerability ID is GSD-2022-1001100. The link to the vulnerability details is provided in the references section.
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
