CVE-2026-97452

8.4

Linux · Kernel

A memory management flaw exists in the Linux kernel ACPICA subsystem where invalid references can be added to local, argument, or debug objects during copy operations.

Executive summary

A high-severity vulnerability in the Linux kernel ACPICA subsystem could allow an attacker with local access to trigger memory corruption and potentially achieve arbitrary code execution.

Vulnerability

This flaw involves improper object reference handling within the acpi_ut_copy_simple_object function. The vulnerability is exploitable by an unauthenticated local user who can interact with the ACPI subsystem to trigger memory corruption.

Business impact

Successful exploitation of this vulnerability could lead to a system crash, unauthorized information disclosure, or the execution of arbitrary code with elevated privileges. Given the CVSS score of 8.4, this represents a significant risk to the integrity and availability of any system running the affected kernel versions, particularly in multi-tenant or shared environments where local access may be achievable.

Remediation

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

Proactive Monitoring: Monitor system logs for kernel oops or segmentation faults, which may indicate attempted exploitation of ACPI subsystem vulnerabilities.

Compensating Controls: Restrict local access to the system and ensure that only authorized users have the capability to execute processes that interact with ACPI-related kernel interfaces.

Exploitation status

Public Exploit Available: No

Analyst recommendation

Due to the critical nature of kernel-level vulnerabilities, it is imperative that administrators prioritize patching this flaw. Systems should be rebooted following the kernel update to ensure the vulnerable code is fully removed from active memory. Ensure that all downstream kernel packages are updated to the versions specified to maintain a secure posture.

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