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

CVE-2026-97446: Linux Kernel ACPICA Use-After-Free Vulnerability

CVE-2026-97446 is a use-after-free flaw in Linux kernel ACPICA that causes NULL pointer dereference crashes when processing malformed _BIX packages. This article covers technical details, system impact, and mitigation strategies.

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-97446 Overview

CVE-2026-97446 is a NULL pointer dereference vulnerability in the Linux kernel's ACPICA subsystem. The flaw resides in the acpi_ns_custom_package() function, which unconditionally dereferences the first element of an ACPI package to read the _BIX version number without validating that the pointer is non-NULL. When firmware returns a _BIX package whose first element is an unresolvable reference, ACPICA evaluates that entry to NULL, triggering a kernel crash. The fix adds a NULL check so the caller receives AE_AML_OPERAND_TYPE instead of panicking.

Critical Impact

Malformed or malicious ACPI firmware tables can trigger a kernel NULL pointer dereference, leading to denial of service on affected Linux systems.

Affected Products

  • Linux kernel ACPICA subsystem
  • Systems evaluating _BIX ACPI method (typically battery-equipped platforms)
  • Multiple stable kernel branches as referenced in upstream commits

Discovery Timeline

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

Technical Details for CVE-2026-97446

Vulnerability Analysis

The vulnerability affects acpi_ns_custom_package() in the ACPICA (ACPI Component Architecture) code of the Linux kernel. ACPICA parses ACPI predefined packages returned by firmware methods. The _BIX (Battery Information Extended) method returns a package whose first element is an integer version field. The function reads this version to determine how to validate the remainder of the package.

Before the fix, the code dereferenced the first element directly:

if ((*Elements)->Common.Type != ACPI_TYPE_INTEGER)

If *Elements is NULL, this dereference faults in kernel context. The patch introduces an explicit NULL check and returns AE_AML_OPERAND_TYPE to the caller, converting a crash into a recoverable error.

Root Cause

The root cause is missing input validation on package elements returned from AML (ACPI Machine Language) evaluation [CWE-476]. ACPICA provides acpi_ns_remove_null_elements() to strip NULL entries from packages, but it intentionally skips ACPI_PTYPE_CUSTOM packages because their fixed-position layout would be broken if elements shifted. As a result, NULL entries can reach acpi_ns_custom_package() and bypass the type check.

Attack Vector

Triggering the bug requires firmware whose _BIX method returns a package with an unresolvable reference as the first element. This can occur on systems with buggy or malformed BIOS or EC firmware, or in environments where firmware tables are modifiable (for example virtualized guests presenting crafted ACPI tables to the guest kernel). Successful triggering causes a kernel oops and denial of service.

// No verified exploit code is available. See upstream commits referenced below
// for the exact source change that adds the NULL check prior to dereferencing
// the first package element.

Detection Methods for CVE-2026-97446

Indicators of Compromise

  • Kernel oops or panic messages referencing acpi_ns_custom_package in the call stack
  • Repeated ACPI evaluation failures returning AE_AML_OPERAND_TYPE after patch application
  • dmesg entries indicating _BIX evaluation errors on battery-equipped systems

Detection Strategies

  • Inventory running kernel versions and compare against patched builds listed in the upstream stable commits
  • Monitor /var/log/kern.log and journalctl -k for NULL pointer dereference traces originating in ACPICA
  • Correlate crash telemetry from endpoints to identify systems with faulty ACPI firmware

Monitoring Recommendations

  • Forward kernel crash dumps and dmesg output to a centralized logging platform for pattern analysis
  • Alert on repeated kernel panics on identical hardware models, which may indicate firmware-level triggers
  • Track firmware and BIOS versions across the fleet to prioritize systems with known buggy ACPI tables

How to Mitigate CVE-2026-97446

Immediate Actions Required

  • Apply the upstream Linux kernel patches referenced below to all affected stable branches
  • Update distribution kernels once vendors publish backported fixes
  • Verify that virtualization hosts do not pass unvalidated ACPI tables to guests

Patch Information

The fix is available in the following upstream commits:

The patch adds a NULL check on the first element of the _BIX package before dereferencing it, returning AE_AML_OPERAND_TYPE to the caller when the element is NULL.

Workarounds

  • Update system firmware or BIOS to a version that returns a well-formed _BIX package
  • Disable ACPI battery drivers on systems where battery reporting is not required and crashes are observed
  • Restrict guest access to custom ACPI tables in virtualized environments
bash
# Verify installed kernel version and check for ACPI-related crash traces
uname -r
dmesg | grep -i -E 'acpi_ns_custom_package|BUG: unable to handle'
journalctl -k --since "7 days ago" | grep -i acpi

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.