Look up another CVE · open CVE-2026-97454 in the interactive tracker
CVE-2026-97454
ACPICA: add boundary checks in acpi_ps_get_next_field()
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-97454 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
Add boundary checks in acpi_ps_get_next_field() to prevent out-of-bounds access.
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/psargs.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
- 7.7 high
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:N/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 | 1d704a9ba665 |
| 2.6.12 | 5.15.222 | 6ecf2a4855a7 |
| 2.6.12 | 6.1.189 | 6509f56df512 |
| 2.6.12 | 6.6.158 | 7d97ecf2a4c7 |
| 2.6.12 | 6.12.111 | add715fc1ef5 |
| 2.6.12 | 6.18.53 | bc5b2158c762 |
| 2.6.12 | 7.2 | e15aa60de025 |
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 truncated bytes are a Field/BankField/IndexField FieldList inside a local DSDT/SSDT, not a network PDU. acpi_bus_init() calls acpi_load_tables() → acpi_tb_load_namespace() → acpi_ns_load_table() → acpi_ns_execute_table() → acpi_ps_parse_aml() → acpi_ps_parse_loop() → acpi_ps_get_next_arg(ARGP_FIELDLIST) → acpi_ps_get_next_field().
- AC:LAttack complexity, low
- A NamedField with fewer than ACPI_NAMESEG_SIZE bytes left before aml_end makes ACPI_MOVE_32_TO_32(&name, parser_state->aml) over-read on every load; AccessField/ExtAccessField similarly ACPI_GET8 past the buffer. The table author sets those AML bytes, with no race.
- PR:NPrivileges required, none
- acpi_bus_init() calls acpi_load_tables() at boot with no capable() check, so a DSDT/SSDT whose FieldList is truncated reaches acpi_ps_get_next_field() with no Linux uid or user-namespace privilege.
- UI:NUser interaction, none
- acpi_ns_execute_table() parses module-level Field/BankField/IndexField opcodes while acpi_load_tables() runs from acpi_bus_init() on ordinary power-on; no victim mount, sysfs open, or module load is required to reach acpi_ps_get_next_field().
- S:UScope, unchanged
- The over-read is of kernel heap adjacent to the ACPI table buffer parsed by host ACPICA in acpi_ps_get_next_field(); it does not cross a KVM/Xen, IOMMU, or sandbox boundary.
- C:HConfidentiality impact, high
- Without aml_end checks, acpi_ps_get_next_field() ACPI_MOVE_32_TO_32-reads a NameSeg and ACPI_GET8-reads Access/ExtAccess bytes past the table heap object (ASAN: 4-byte read past a 175-byte allocation). ARGP_FIELDLIST keeps looping while aml < pkg_end from the attacker-chosen Field PkgLength, so the walk is not capped to a few header bytes.
- I:NIntegrity impact, none
- ASAN reports a READ of size 4 in AcpiPsGetNextField; ACPI_MOVE_32_TO_32 and ACPI_GET8 only fill local name/access_type variables and the newly allocated field op. The function never stores through parser_state->aml, so there is no out-of-bounds write.
- A:HAvailability impact, high
- The ASAN heap-buffer-overflow is the NamedField ACPI_MOVE_32_TO_32 immediately past the 175-byte table allocation (shadow redzone). A read off that slab object during acpi_load_tables() can oops or panic the kernel at boot.