CVE-2026-97451

HIGHPre-NVD 8.48.4—
EchelonGraph scoreHIGH confidence

Score 8.4 from GitHub Security Advisory (severity: HIGH) published 2026-09-24. A secondary CVSS source baseline 8.4; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
8.4EG
EchelonGraph verdictPlan mitigationSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.1%CVSS: 8.4Exploit: None knownExposed services: Not assessed

No fix is confirmed yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for the fix.

In the Linux kernel, the following vulnerability has been resolved:

ACPICA: Fix integer overflow in acpi_ex_opcode_3A_1T_1R() (mid_op)

Add overflow check for Index + Length to prevent integer overflow when calculating the truncation length. This prevents negative size parameter being passed to memcpy().

CVSS v3
8.4
EG Score
8.4HIGHhigh confidence
EG Risk
42
EG Risk 42/100CISA SSVC

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity84% × 45%
Exploitation0% × 40%
Automatability30% × 15%
CISA SSVC: Track at low or medium mission impact; Track or Attend at high (mission-essential systems).
Action: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.
EPSS PROB
0.1%
EPSS %ILE
2nd
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Track or Attend at high (mission-essential systems).

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.

Exploitation none (no KEV listing, exploit record or EPSS ≥ 50%) · Automatable unknown (not published for this CVE) · Technical impact partial (CVSS below 9.0). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

September 24, 2026

Last Modified

October 3, 2026

Advisory Details (3)

Auto-updated Sep 25, 2026
No patch confirmed yet.
generic

ACPICA: Fix integer overflow in acpi_ex_opcode_3A_1T_1R() (mid_op) - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/d0d89f2e16a874e0f8fb17045da293e8bedf8b21
generic

ACPICA: Fix integer overflow in acpi_ex_opcode_3A_1T_1R() (mid_op) - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/b96401812cbfbb4803faabeefa1f20b8562268b3
generic

ACPICA: Fix integer overflow in acpi_ex_opcode_3A_1T_1R() (mid_op) - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/0e2021f49e64b3c8a9aa880d0c62a218bfe147ce

Vendor Advisories for CVE-2026-97451(2)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(4 across 3 ecosystems)
Debian:12(2)
PackageVulnerable rangeFix by version rangeDependents
linux6.1.106-1 ... 7.2~rc7-1~exp1 (360 versions)
  • every version on: no fix on record
—
linux-6.126.12.100-1~deb12u1, 6.12.101-1~deb12u1, 6.12.107-1~deb12u1
  • every version up to 6.12.111-1~deb12u1: fixed in 6.12.111-1~deb12u1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 6.12.96-1 (35 versions)
  • every version up to 6.12.111-1: fixed in 6.12.111-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 7.2~rc7-1~exp1 (179 versions)
  • every version up to 7.2.6-1: fixed in 7.2.6-1
—

Data Freshness Timeline

(refreshed 41× in last 7d / 60× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-10-05 02:58 UTCEG score recompute
  2. 2026-10-05 02:58 UTCVendor advisory
  3. 2026-10-05 02:58 UTCGHSA enrichment
  4. 2026-10-04 23:23 UTCEPSS rescore
  5. 2026-10-04 13:46 UTCVendor advisory
  6. 2026-10-04 13:46 UTCGHSA enrichment
  7. 2026-10-04 00:38 UTCEG score recompute
  8. 2026-10-04 00:38 UTCVendor advisory
  9. 2026-10-04 00:38 UTCGHSA enrichment
  10. 2026-10-03 14:26 UTCEPSS rescore
  11. 2026-10-03 11:31 UTCVendor advisory
  12. 2026-10-03 11:31 UTCGHSA enrichment
  13. 2026-10-03 06:45 UTCEG score recompute
  14. 2026-10-03 06:45 UTCVendor advisory
  15. 2026-10-03 06:45 UTCGHSA enrichment
  16. 2026-10-02 17:57 UTCEPSS rescore
  17. 2026-10-02 17:38 UTCVendor advisory
  18. 2026-10-02 17:37 UTCGHSA enrichment
  19. 2026-10-02 04:30 UTCEG score recompute
  20. 2026-10-02 04:30 UTCVendor advisory
  21. 2026-10-02 04:30 UTCGHSA enrichment
  22. 2026-10-01 19:51 UTCEPSS rescore
  23. 2026-10-01 15:18 UTCVendor advisory
  24. 2026-10-01 15:18 UTCGHSA enrichment
  25. 2026-10-01 02:11 UTCEG score recompute
Show 35 more
  1. 2026-10-01 02:11 UTCVendor advisory
  2. 2026-10-01 02:11 UTCGHSA enrichment
  3. 2026-09-30 15:04 UTCEPSS rescore
  4. 2026-09-30 13:04 UTCVendor advisory
  5. 2026-09-30 13:04 UTCGHSA enrichment
  6. 2026-09-29 23:55 UTCEG score recompute
  7. 2026-09-29 23:55 UTCVendor advisory
  8. 2026-09-29 23:54 UTCGHSA enrichment
  9. 2026-09-29 08:43 UTCEG score recompute
  10. 2026-09-29 08:43 UTCVendor advisory
  11. 2026-09-29 08:43 UTCGHSA enrichment
  12. 2026-09-28 19:36 UTCEG score recompute
  13. 2026-09-28 19:36 UTCVendor advisory
  14. 2026-09-28 19:35 UTCGHSA enrichment
  15. 2026-09-28 13:52 UTCEPSS rescore
  16. 2026-09-28 13:52 UTCEPSS rescore
  17. 2026-09-28 06:24 UTCEG score recompute
  18. 2026-09-28 06:24 UTCGHSA enrichment
  19. 2026-09-28 05:48 UTCEG score recompute
  20. 2026-09-28 05:48 UTCGHSA enrichment
  21. 2026-09-27 22:58 UTCGHSA enrichment
  22. 2026-09-27 09:51 UTCGHSA enrichment
  23. 2026-09-26 20:44 UTCEG score recompute
  24. 2026-09-26 20:43 UTCGHSA enrichment
  25. 2026-09-26 15:59 UTCEPSS rescore
  26. 2026-09-26 07:33 UTCEG score recompute
  27. 2026-09-26 07:33 UTCGHSA enrichment
  28. 2026-09-25 18:24 UTCEG score recompute
  29. 2026-09-25 18:24 UTCGHSA enrichment
  30. 2026-09-25 05:17 UTCEG score recompute▲ 8.40
  31. 2026-09-25 05:17 UTCGHSA enrichment
  32. 2026-09-25 05:16 UTCMITRE cvelistV5CVSS v3 → 8.4 · severity → HIGH
  33. 2026-09-24 17:33 UTCNVD update
  34. 2026-09-24 16:28 UTCEG score recompute
  35. 2026-09-24 16:26 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-97451?
CVE-2026-97451 is a high vulnerability published on September 24, 2026. In the Linux kernel, the following vulnerability has been resolved: ACPICA: Fix integer overflow in acpiexopcode3A1T1R() (midop) Add overflow check for Index + Length to prevent integer overflow when calculating the truncation length. This prevents negative size parameter being passed to memcpy().
When was CVE-2026-97451 disclosed?
CVE-2026-97451 was first published on September 24, 2026, with the most recent update on October 3, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-97451 actively exploited?
CVE-2026-97451 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.1% probability of exploitation in the next 30 days (2nd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-97451?
CVE-2026-97451 has a CVSS base score of 8.4 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-97451?
No fix for CVE-2026-97451 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix. The vendor advisories EchelonGraph has for CVE-2026-97451 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-97451

Explore →

Is Your Infrastructure Affected by CVE-2026-97451?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs