A use‑after‑free flaw exists in the function that terminates ACPI control methods. In this scenario, a dangling pointer to method locals and arguments can be used to read or write memory after the object is freed, which may corrupt kernel data or cause arbitrary code execution. The impact on confidentiality, integrity, and availability depends on how the flaw is triggered, but it carries the inherent risk of privilege escalation or system instability.

The vulnerability affects the Linux kernel through its ACPI subsystem. It is present in any kernel that has not yet been updated with the commit that addresses the issue. No specific version numbers are provided in the current data, but the patch is available in the upstream repository.

The severity of a kernel‑level use‑after‑free is high, as indicated by a CVSS score of 8.4. EPSS is < 1% and the flaw is not in the CISA KEV catalog, suggesting that widespread exploitation is not yet documented. Attackers would need to supply a crafted ACPI request or control method, so the likely attack vector is from firmware or userland interacting with ACPI. Given the kernel nature of the flaw, successful exploitation could result in system compromise or a reboot.