CVE-2026-97455

8.4

Linux · Kernel

A use-after-free vulnerability in the Linux kernel ACPICA subsystem allows local attackers to potentially achieve arbitrary code execution or cause system instability.

Executive summary

A high-severity use-after-free vulnerability in the Linux kernel ACPICA component poses a significant risk of local privilege escalation and system compromise.

Vulnerability

This is a use-after-free vulnerability located in the acpi_ds_terminate_control_method function, caused by improper clearing of references to method locals and arguments. The vulnerability is exploitable by a local attacker with no specific privileges required (AV:L/AC:L/PR:N).

Business impact

The flaw carries a CVSS score of 8.4, reflecting the potential for complete loss of confidentiality, integrity, and availability of the host system. Successful exploitation allows a local user to execute arbitrary code with kernel-level privileges, which can lead to total system takeover, data exfiltration, or the installation of persistent rootkits.

Remediation

Immediate Action: Update the Linux kernel to version 6.12.111, 6.18.53, or later as provided by your distribution maintainer.

Proactive Monitoring: Monitor system logs for kernel panics or unexpected crashes associated with ACPI-related tasks, which may indicate attempted exploitation.

Compensating Controls: Restrict access to local system consoles and limit the ability of untrusted users to execute arbitrary code or load kernel modules on high-value systems.

Exploitation status

Public Exploit Available: Unknown

Analyst recommendation

Given the high CVSS score and the critical nature of the affected kernel subsystem, security teams should prioritize patching this vulnerability in all Linux environments. Ensure that kernel updates are tested in staging before deployment to production systems, and verify that the target versions 6.12.111 or 6.18.53 are applied to eliminate the underlying memory management flaw.

More Linux CVEs all →

History

  1. Disclosed CVE record published
  2. Collected by CVE Brief via github
  3. Analyst report written
  4. Published in the daily brief high section

Sources