ACPI: custom_method: fix potential use-after-free issue in Kernel

Kernel Updated 02 Oct 2025

Summary

31/05/2021
N/A
No i
Unrated
Not published

GSD-2021-1000159: ACPI: custom_method: fix potential use-after-free issue. Affects Kernel versions >= 03d1571d9513369c17e6848476763ebbd10ec2cb, < 62dc2440ebb552aa0d7f635e1697e077d9d21203. No fix is published. How to fix ↓

Free scan

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.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The Kernel is a fundamental component of the Linux operating system that manages core system functions, including hardware communication and process management. It provides an interface between the hardware and software layers, allowing applications to interact with the underlying system resources. The ACPI (Advanced Configuration and Power Interface) subsystem within the Kernel handles power management and device configuration. One of the features of ACPI is custom_method, which allows users to define their own ACPI methods. However, a potential use-after-free issue has been identified in the custom_method implementation.

Vulnerability Detail

The vulnerability arises from a use-after-free issue in the ACPI custom_method implementation. This type of vulnerability occurs when a program continues to use a memory reference after it has been freed, leading to potential memory corruption or arbitrary code execution. An attacker could potentially exploit this vulnerability to execute malicious code or crash the system. The vulnerability was introduced in version v5.4 of the Linux Kernel and has been fixed in version v5.10.36.

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

As this vulnerability has been fixed in the latest version of the Linux Kernel, there is no specific workaround available. It is strongly advised to update to the patched version to mitigate the risk.

Conclusion

The ACPI custom_method vulnerability in the Linux Kernel poses a potential risk of arbitrary code execution or system crashes. It is crucial to update the Kernel to version v5.10.36 or later, which includes the necessary fix. Failure to apply the patch may leave systems vulnerable to exploitation. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for Kernel →

Share this vulnerability

FAQ

The vulnerability could potentially allow an attacker to execute arbitrary code or crash the system.

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, and Vulert will analyze it for any open-source vulnerabilities, including this one.

At the time of this report, there are no known exploits for this vulnerability. However, it is crucial to apply the patch promptly to prevent potential exploitation.

No, only versions from v5.4 to v5.10.35 are affected. The vulnerability has been fixed in version v5.10.36 and later.

No, the recommended mitigation is to update the Linux Kernel to the latest version, as it includes the necessary patch to address the vulnerability.

Related vulnerabilities

Recent vulnerabilities recorded for Kernel.

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 →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback