Skip to content
major vulnerability· requires attention

Kernel-level ACPICA integer overflow affects widely deployed Linux kernels; can enable local privilege escalation or widespread instability across servers, cloud VMs, endpoints.

Systems

CVE-2026-97451

8.4
High
EPSS n/aPatch availableSep 25, 2026

ACPICA integer overflow in Linux kernel enables kernel memory corruption (LPE/DoS)

common questions

Is CVE-2026-97451 being exploited?

Not confirmed. CVE-2026-97451 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked.

How severe is CVE-2026-97451?

CVE-2026-97451 is rated High with a CVSS score of 8.4. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-97451?

Yes. A fix has been recorded for CVE-2026-97451. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-97451 affect?

CVE-2026-97451 affects Linux kernel (ACPICA / ACPI subsystem), Linux distributions using affected stable kernels, Cloud VMs, servers, desktops, embedded Linux devices. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-97451?

Install kernel updates containing the ACPICA fix and reboot affected hosts immediately.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
Linux kernel (ACPICA / ACPI subsystem)Linux distributions using affected stable kernelsCloud VMs, servers, desktops, embedded Linux devices
impact

Integer overflow in acpi_ex_opcode_3A_1T_1R() can cause kernel memory corruption, enabling local privilege escalation or kernel crash (DoS).

action required

Immediate action required

affected versions
Linux Linux
  • affected>= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and < d0d89f2e16a874e0f8fb17045da293e8bedf8b21
  • affected>= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and < b96401812cbfbb4803faabeefa1f20b8562268b3
  • affected>= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and < 0e2021f49e64b3c8a9aa880d0c62a218bfe147ce
  • affected< 6.12.111
  • affected< 6.18.53
vendor says fixed in>= 6.12.111 and <= 6.12.*, >= 6.18.53 and <= 6.18.*, >= 7.2 and <= *

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free