Look up another CVE · open CVE-2026-97444 in the interactive tracker
CVE-2026-97444
ACPICA: add boundary checks 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-97444 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_namestring() and acpi_ps_peek_opcode() 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
drivers/acpi/acpica/psparse.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 | 3a8c1efc0fd3 |
| 2.6.12 | 5.15.222 | c917df56b737 |
| 2.6.12 | 6.1.189 | 4f03d84c95a5 |
| 2.6.12 | 6.6.158 | 38ee32a9ace6 |
| 2.6.12 | 6.12.111 | 253d7272d01d |
| 2.6.12 | 6.18.53 | 4de2cffef5e6 |
| 2.6.12 | 7.2 | bdc357540129 |
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 AML that acpi_ps_get_next_namestring() and acpi_ps_peek_opcode() over-read is the platform DSDT/SSDT stream parsed by acpi_ns_execute_table() from acpi_load_tables() in acpi_bus_init(); those bytes come from local firmware tables, not from a network protocol message.
- AC:LAttack complexity, low
- A DSDT/SSDT whose namestring (AML_MULTI_NAME_PREFIX count or a run of '\'/'^' prefixes) or final opcode sits against the AML buffer end makes acpi_ps_get_next_namestring() and acpi_ps_peek_opcode() read past parser_state->aml_end on every acpi_load_tables() parse; the table author sets those bytes and no race is required.
- PR:NPrivileges required, none
- acpi_bus_init() calls acpi_load_tables() → acpi_tb_load_namespace() → acpi_ns_load_table() → acpi_ns_execute_table() at boot with no capability check, so the OOB in acpi_ps_get_next_namestring()/acpi_ps_peek_opcode() fires on firmware AML before any user account exists.
- UI:NUser interaction, none
- acpi_load_tables() parses the DSDT/SSDT automatically during acpi_bus_init() at boot; the victim does not need to mount media, open a file, or otherwise interact.
- S:UScope, unchanged
- acpi_ns_lookup()'s ACPI_MOVE_32_TO_32 of an over-long nameseg and acpi_ps_peek_opcode()'s ACPI_GET8 over-read kernel memory adjacent to the mapped AML buffer inside the host kernel; this is not a VM escape or IOMMU bypass.
- C:HConfidentiality impact, high
- acpi_ps_get_next_namestring() does not cap '\'/'^' prefix walking or the AML_MULTI_NAME_PREFIX count byte, then acpi_ns_lookup() copies up to 255 four-byte namesegs via ACPI_MOVE_32_TO_32 past aml_end, so the out-of-bounds read is not limited to a few bytes.
- I:NIntegrity impact, none
- The demonstrated faults are heap-buffer-overflow reads (4 bytes in acpi_ns_lookup, 1–2 bytes in acpi_ps_peek_opcode); the patched functions only advance parser_state->aml and return a namestring pointer or opcode, and do not write past the AML buffer.
- A:HAvailability impact, high
- The same over-read past the AML allocation in acpi_ns_lookup()/acpi_ps_peek_opcode() during acpi_load_tables() can touch unmapped memory and oops or panic the kernel at boot.