ACPI: custom_method: Fix Potential Use-After-Free Issue in Kernel
Summary
GSD-2021-1000183: ACPI: custom_method: fix potential use-after-free issue. Affects Kernel versions >= 03d1571d9513369c17e6848476763ebbd10ec2cb, < 72814a94c38a33239793f7622cec6ace1e540c4b. 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 critical component of the Linux operating system that manages communication between hardware and software. It provides essential functions and services to enable the proper functioning of the system. ACPI (Advanced Configuration and Power Interface) is a standard that defines hardware interfaces for power management and configuration. The ACPI custom_method is a feature that allows users to define their own custom ACPI methods. However, a vulnerability has been discovered in the custom_method implementation that could lead to a use-after-free issue.
Vulnerability Detail
The vulnerability in the ACPI custom_method implementation could potentially result in a use-after-free issue. A use-after-free vulnerability occurs when a program continues to use a memory area after it has been freed, which can lead to unpredictable behavior and potentially be exploited by an attacker. In this case, the use-after-free issue arises due to improper handling of custom ACPI methods, which could be triggered by an attacker with local access to the system. 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. The recommended solution is to update the Linux Kernel to the fixed version.
Conclusion
The ACPI custom_method vulnerability in the Linux Kernel has been identified and fixed in version v5.4.118. Users are advised to update their Kernel to the fixed version to mitigate the risk of potential exploitation. Regularly updating the Kernel is recommended to ensure the latest security patches are applied. For further support on vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
The impact of this vulnerability is not yet proven. However, a use-after-free vulnerability can potentially lead to unpredictable behavior and may be exploited by attackers with local access to the system.
You can use Vulert Playground (https://vulert.com/scanner) to check if your system is affected by this vulnerability. Simply upload your manifest file (e.g., package-lock.json) to the playground, and it will alert you in real-time if your system is vulnerable.
No, this vulnerability requires local access to the system to be exploited.
There are no known instances of this vulnerability being exploited at the moment.
For further support on vulnerability remediation, you can reach out to info@devnack.com.
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
