CVE-2026-64227

What the bug is

Since every platform driver can be forced to match a device that doesn't match its list of device IDs because of device_match_driver_override(), platform drivers that rely on the existence of a device's ACPI companion object should verify its presence. Accordingly, add requisite ACPI_COMPANION() or ACPI_HANDLE() checks against NULL to 13 platform drivers handling core ACPI devices. Also change the value returned by the ACPI thermal zone driver when the device's ACPI companion is not present to -ENODEV for consistency with the other drivers.

Where it lives

The fix touches these files. If the subsystem is one you do not use, the practical exposure is lower, though the package is still the vulnerable one.

drivers/acpi/ac.c
drivers/acpi/acpi_pad.c
drivers/acpi/acpi_tad.c
drivers/acpi/battery.c
drivers/acpi/button.c
drivers/acpi/ec.c
drivers/acpi/hed.c
drivers/acpi/nfit/core.c
drivers/acpi/pfr_telemetry.c
drivers/acpi/pfr_update.c
drivers/acpi/sbs.c
drivers/acpi/sbshc.c

What this is

ACPIMAINTAINERS section matched on drivers/acpi/ · linux-acpi@vger.kernel.org · Supported

Kernel module

ac

Check it on the machine

grep -wE 'CONFIG_ACPI|CONFIG_ACPI_AC' /boot/config-$(uname -r)

Reads the booted kernel's own configuration, on the machine and nowhere else. =y is built in, =m is a module, and an is not set line means the code is not there.

lsmod | grep -w ac

Prints a line if that module is loaded right now, and nothing if it is not. One that is not loaded can still be loaded later by anything that needs it.

Show whether Debian builds this, per release

Debian builds this, but not on every flavour. At least one release below builds the code on some of its kernel flavours and not on others, so the answer depends on the architecture and flavour installed.

• bookwormBnot built on amd64/cloud-amd64, armhf/armmp, armhf/armmp-lpae, armhf/rt/armmp, ppc64el/powerpc64le
• trixieBnot built on amd64/cloud-amd64, armel/rpi, armhf/armmp, armhf/armmp-lpae, armhf/rt/armmp, ppc64el/powerpc64le, ppc64el/powerpc64le-64k, s390x/s390x
• forky, sidBnot built on amd64/cloud-amd64, armhf/armmp, armhf/armmp-lpae, ppc64el/powerpc64le, ppc64el/powerpc64le-64k, s390x/s390x
• bookworm · linux-6.12Bnot built on amd64/cloud-amd64, armhf/armmp, armhf/armmp-lpae, armhf/rt/armmp, ppc64el/powerpc64le, ppc64el/powerpc64le-64k

B

built in on some, a module on others, absent on the rest

Build switches

CONFIG_ACPI, CONFIG_ACPI_AC

Reads as

all on means the file is compiled; any one off means it is not.

From the configuration Debian publishes for every kernel flavour it builds. It covers only the architectures Debian ships a linux-config package for, and nothing about a kernel you built yourself. Debian's own status above stays authoritative about the source package.MAINTAINERS kbuild Makefiles Debian linux-config packages

Signals

Published

2026-07-24 (3 months ago)source

CVSS

no vector published, unrated

Attack vector

not published

EPSS

0.16%, higher than 5.0% of all CVEssource

CISA KEV

not listedthe KEV catalogue

Debian urgency

unimportantsource

Subsystem

drivers/acpi

Upstream fixes

The versions the CNA records as introducing and fixing this, and the commit for each. source

Introduced	Fixed in	Commit
6.7	6.12.97	a9451bf56123
6.7	6.18.40	34f4d0e4e506
6.7	7.0.11	612ddab8fce0
6.7	7.1	e4865a56d013

Debian advisories