Skip to main content
Vulnerability Database/CVE-2026-97444

CVE-2026-97444: Linux Kernel Buffer Overflow Vulnerability

CVE-2026-97444 is a buffer overflow flaw in the Linux kernel ACPICA component that could allow out-of-bounds memory access. This post explains the technical details, affected kernel versions, and mitigation steps.

Published:

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

CVE-2026-97444 Overview

CVE-2026-97444 is an out-of-bounds access vulnerability in the Linux kernel's ACPICA (ACPI Component Architecture) subsystem. The flaw affects the acpi_ps_get_next_namestring() and acpi_ps_peek_opcode() parser functions, which lacked boundary checks when processing ACPI tables. A local attacker able to supply crafted ACPI data can trigger out-of-bounds reads that lead to kernel memory corruption or system crashes. The vulnerability was addressed upstream by adding explicit boundary validation inside the two affected parser routines.

Critical Impact

Local attackers can trigger out-of-bounds access in kernel-mode ACPI parsing, resulting in high confidentiality and availability impact on affected Linux systems.

Affected Products

  • Linux kernel (ACPICA subsystem)
  • acpi_ps_get_next_namestring() parser function
  • acpi_ps_peek_opcode() parser function

Discovery Timeline

  • 2026-09-24 - CVE-2026-97444 published to NVD
  • 2026-09-25 - Last updated in NVD database

Technical Details for CVE-2026-97444

Vulnerability Analysis

The vulnerability resides in the ACPICA parser code shared by the Linux kernel. Two parser helpers, acpi_ps_get_next_namestring() and acpi_ps_peek_opcode(), advanced through ACPI Machine Language (AML) byte streams without validating that the read pointer remained within the bounds of the input buffer. When the parser encountered a malformed or truncated AML stream, it continued reading past the end of the allocated region.

This out-of-bounds read occurs in kernel context during ACPI table processing. Consequences include disclosure of adjacent kernel memory, dereference of invalid pointers derived from the read data, and kernel panics. Because ACPI parsing runs with full kernel privileges, memory corruption in this path can affect overall system stability and confidentiality.

Root Cause

The root cause is missing input validation in two low-level parser routines. Both functions assumed the AML byte stream was well-formed and operated on raw pointer arithmetic without comparing the current position against the buffer end. The upstream fix adds explicit boundary checks before each read operation inside acpi_ps_get_next_namestring() and acpi_ps_peek_opcode().

Attack Vector

Exploitation requires local access to the target system. An attacker with the ability to load or supply malicious ACPI tables, for example through firmware-level access, kernel modules, or interfaces that pass AML data into the parser, can craft input that forces the parser to read beyond buffer boundaries. No user interaction is required, and the attack complexity is low. The resulting impact includes denial of service through kernel panic and potential disclosure of sensitive kernel memory.

No verified public exploit code is available. Technical details of the fix are documented in the upstream Linux kernel commits.

Detection Methods for CVE-2026-97444

Indicators of Compromise

  • Unexpected kernel panics or oops messages referencing acpi_ps_get_next_namestring or acpi_ps_peek_opcode in dmesg or /var/log/kern.log.
  • KASAN (Kernel Address Sanitizer) reports flagging out-of-bounds reads in the ACPI parser code path.
  • Abnormal ACPI table loads or /sys/firmware/acpi/tables modifications on hardened systems.

Detection Strategies

  • Compare installed kernel versions against the fixed revisions identified by upstream commits 253d7272, 4de2cffe, and bdc35754.
  • Enable KASAN or KMSAN in test environments to surface boundary violations in ACPI parsing code during fuzzing.
  • Audit kernel crash reports for signatures matching the ACPI parser functions patched by this fix.

Monitoring Recommendations

  • Collect and centralize dmesg output from Linux fleets to detect recurring ACPI parser faults.
  • Monitor kernel package versions across endpoints to confirm patched builds are deployed.
  • Alert on unexpected use of acpi_configfs or custom ACPI table loading interfaces on production hosts.

How to Mitigate CVE-2026-97444

Immediate Actions Required

  • Apply the latest stable Linux kernel updates from your distribution that include the ACPICA boundary-check fix.
  • Restrict local access on multi-user systems and prevent untrusted users from loading custom ACPI tables.
  • Disable or restrict CONFIG_ACPI_CUSTOM_METHOD and CONFIG_ACPI_TABLE_UPLOAD where not required.

Patch Information

The fix adds boundary checks inside acpi_ps_get_next_namestring() and acpi_ps_peek_opcode(). Upstream patches are available in the following commits: Linux Kernel Commit 253d7272, Linux Kernel Commit 4de2cffe, and Linux Kernel Commit bdc35754. Deploy vendor-supplied kernel updates that incorporate these commits.

Workarounds

  • Enforce Secure Boot and signed kernel modules to prevent injection of malicious ACPI code at boot time.
  • Remove the acpi_configfs module on systems that do not need runtime ACPI table loading.
  • Limit physical and administrative access to systems where firmware-level attacks are plausible.
bash
# Verify running kernel and check for ACPI custom table interface
uname -r
lsmod | grep acpi_configfs
# Remove the module if not required
sudo modprobe -r acpi_configfs

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

Experience the Most Advanced Cybersecurity Platform

See how the world’s most intelligent, autonomous cybersecurity platform can protect your organization today and into the future.