Look up another CVE · open CVE-2026-97450 in the interactive tracker
CVE-2026-97450
ACPICA: validate handler object type in two places
Published 2026-09-24 (24 days ago) by the Linux kernel CNA. Subsystem drivers/acpi. Debian urgency: not yet assigned.
What to do, per Debian release
Debian's own status for CVE-2026-97450 in every release this site tracks, and what each one means in practice. Every status below is the one the Debian Security Team publishes for this CVE. source
| Release | Status | Version | What this means |
|---|---|---|---|
| Debian 12bookworm | fixedDLA-4841-1 · 2026-10-17 · text | 6.1.190-1 | Update the kernel and reboot. DLA-4841-1 shipped the fix on 2026-10-17, in 6.1.190-1. A running kernel keeps the old code until the machine restarts. |
| Debian 13trixie | fixedDSA-6528-1 · 2026-09-29 · text | 6.12.111-1 | Update the kernel and reboot. DSA-6528-1 shipped the fix on 2026-09-29, in 6.12.111-1. A running kernel keeps the old code until the machine restarts. |
| Debian 14forky | fixed | 7.2.6-1 | Update the kernel and reboot. Fixed in 7.2.6-1. A running kernel keeps the old code until the machine restarts. |
| Debian unstablesid | fixed | 7.2.6-1 | Update the kernel and reboot. Fixed in 7.2.6-1. A running kernel keeps the old code until the machine restarts. |
| Debian 12bookworm · linux-6.12 | fixedDLA-4817-1 · 2026-10-04 · text | 6.12.111-1~deb12u1 | Update the kernel and reboot. DLA-4817-1 shipped the fix on 2026-10-04, in 6.12.111-1~deb12u1. A running kernel keeps the old code until the machine restarts. |
The vulnerability
What the bug is
ACPICA: validate handler object type in acpi_ev_has_default_handler() and acpi_ev_find_region_handler().
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/acpica/evhandler.c
- What this is
- ACPI COMPONENT ARCHITECTURE (ACPICA)MAINTAINERS section matched on drivers/acpi/acpica/ · linux-acpi@vger.kernel.org · Supported
Check it on the machine
grep -w CONFIG_ACPI /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.
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.
- bookwormYnot built on armhf/armmp, armhf/armmp-lpae, armhf/rt/armmp, ppc64el/powerpc64le
- trixieYnot built on armel/rpi, armhf/armmp, armhf/armmp-lpae, armhf/rt/armmp, ppc64el/powerpc64le, ppc64el/powerpc64le-64k, s390x/s390x
- forky, sidYnot built on armhf/armmp, armhf/armmp-lpae, ppc64el/powerpc64le, ppc64el/powerpc64le-64k, s390x/s390x
- bookworm · linux-6.12Ynot built on armhf/armmp, armhf/armmp-lpae, armhf/rt/armmp, ppc64el/powerpc64le, ppc64el/powerpc64le-64k
- Y
- built in where it is built at all; some flavours do not build it
- Build switch
- CONFIG_ACPI
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-09-24 (24 days ago)source
- CVSS
- 8.4 high
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:Hsource recompute it - Attack vector
- local (AV:L)source
- EPSS
- 0.14%, higher than 3.1% of all CVEssource
- CISA KEV
- not listedthe KEV catalogue
- Debian urgency
- not yet assignedsource
- 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 |
|---|---|---|
| 2.6.12 | 5.10.271 | 7af2da201623 |
| 2.6.12 | 5.15.222 | 9d9fbf6b895a |
| 2.6.12 | 6.1.189 | e98825650c2e |
| 2.6.12 | 6.6.158 | 254e304f68dc |
| 2.6.12 | 6.12.111 | bfd981d35ed3 |
| 2.6.12 | 6.18.53 | 4c977d57a784 |
| 2.6.12 | 7.2 | c5296da2d516 |
Debian advisories
| Advisory | Date | Shipped to | Debian |
|---|---|---|---|
| DLA-4841-1 | 2026-10-17 | bookworm 6.1.190-1 | tracker |
| DLA-4817-1 | 2026-10-04 | bookworm 6.12.111-1~deb12u1 | tracker |
| DSA-6528-1 | 2026-09-29 | trixie 6.12.111-1 | tracker |
Why the CNA scored it this way
Quoted from the kernel CNA's own scoring file, word for word. A highlighted metric carries the most severe value CVSS v3.1 defines for it, which is what pushes the score up. source
- AV:LAttack vector, local
- The malformed AML that leaves a non-ACPI_TYPE_LOCAL_ADDRESS_HANDLER object as common_notify.handler arrives in a DSDT/SSDT. acpi_ev_find_region_handler() is reached from acpi_ev_install_space_handler() via acpi_install_address_space_handler(ACPI_ROOT_OBJECT) in ec_install_handlers()/acpi_ipmi_init(), and from acpi_ev_initialize_region() during acpi_tb_load_namespace(); no network message carries those bytes.
- AC:LAttack complexity, low
- acpi_ev_install_space_handler() skips the DEVICE/PROCESSOR/THERMAL type check for acpi_gbl_root_node, so CopyObject of a Buffer onto `\` makes obj_desc->common_notify.handler overlay Buffer.aml_start. A later handler install or OperationRegion init walks address_space.next on every run; the table author sets those objects and no race is required.
- PR:NPrivileges required, none
- acpi_bus_init() calls acpi_load_tables() which executes module-level AML, then acpi_initialize_objects() → acpi_ev_initialize_op_regions() → acpi_ev_has_default_handler(acpi_gbl_root_node), and ec_install_handlers() calls acpi_install_address_space_handler(ACPI_ROOT_OBJECT) with no capable() check; a compromised DSDT/SSDT needs no Linux account.
- UI:NUser interaction, none
- Module-level AML runs in acpi_ns_execute_table() during acpi_load_tables(), and acpi_ev_find_region_handler() then runs from acpi_ev_initialize_op_regions() and from EC/IPMI/PCC handler install in boot/probe; that is ordinary power-on with no mount or file-open by a victim.
- S:UScope, unchanged
- The type-confused walk in acpi_ev_find_region_handler()/acpi_ev_has_default_handler() and the stores in acpi_ev_attach_region() stay inside the host ACPICA operand-object heap and do not cross a KVM/Xen, IOMMU, or sandbox boundary.
- C:HConfidentiality impact, high
- Without the ACPI_TYPE_LOCAL_ADDRESS_HANDLER check, acpi_ev_find_region_handler() reads address_space.space_id and follows address_space.next from a wrong-typed operand (or from AML bytes overlaying common_notify.handler), an unbounded kernel overread of adjacent heap or attacker-chosen addresses rather than a few header bytes.
- I:HIntegrity impact, high
- acpi_ev_initialize_region() passes the type-confused pointer from acpi_ev_find_region_handler() to acpi_ev_attach_region(), which writes region_list and handler links through it; a matching fake space_id makes acpi_ev_address_space_dispatch() later invoke address_space.handler as a function pointer, which is type-confusion control-flow hijack.
- A:HAvailability impact, high
- Walking address_space.next from a non-handler object (the ASAN global-buffer-overflow in AcpiEvFindRegionHandler on issue26.aml) dereferences an invalid pointer and oopses or panics the kernel during acpi_ev_install_space_handler() or acpi_ev_initialize_region().