CVE-2026-97445

HIGHPre-NVD 7.77.7—
EchelonGraph scoreHIGH confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
7.7EG
EchelonGraph verdictPlan mitigationSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 7.7Exploit: 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: Enhance buffer validation in acpi_ut_walk_aml_resources()

Enhance buffer validation in acpi_ut_walk_aml_resources() to prevent buffer overflows.

CVSS v3
7.7
EG Score
7.7HIGHhigh confidence
EG Risk
39
EG Risk 39/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
Severity77% × 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.2%
EPSS %ILE
4th
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: Enhance buffer validation in acpi_ut_walk_aml_resources() - kernel/git/stable/linux.git - Linux kernel stable tree

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

ACPICA: Enhance buffer validation in acpi_ut_walk_aml_resources() - kernel/git/stable/linux.git - Linux kernel stable tree

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

ACPICA: Enhance buffer validation in acpi_ut_walk_aml_resources() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/b2e21fe8c3361c3d0d57ee56d359bea9b51fda3d

Vendor Advisories for CVE-2026-97445(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 44× in last 7d / 66× 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 08:55 UTCEG score recompute
  2. 2026-10-05 08:55 UTCVendor advisory
  3. 2026-10-05 08:54 UTCGHSA enrichment
  4. 2026-10-04 23:23 UTCEPSS rescore
  5. 2026-10-04 21:31 UTCVendor advisory
  6. 2026-10-04 21:31 UTCGHSA enrichment
  7. 2026-10-04 10:11 UTCVendor advisory
  8. 2026-10-04 10:11 UTCGHSA enrichment
  9. 2026-10-03 22:51 UTCEG score recompute
  10. 2026-10-03 22:51 UTCVendor advisory
  11. 2026-10-03 22:51 UTCGHSA enrichment
  12. 2026-10-03 14:26 UTCEPSS rescore
  13. 2026-10-03 11:31 UTCVendor advisory
  14. 2026-10-03 11:31 UTCGHSA enrichment
  15. 2026-10-03 03:02 UTCEG score recompute
  16. 2026-10-03 03:02 UTCVendor advisory
  17. 2026-10-03 03:02 UTCGHSA enrichment
  18. 2026-10-02 17:57 UTCEPSS rescore
  19. 2026-10-02 15:42 UTCVendor advisory
  20. 2026-10-02 15:42 UTCGHSA enrichment
  21. 2026-10-02 04:22 UTCEG score recompute
  22. 2026-10-02 04:22 UTCVendor advisory
  23. 2026-10-02 04:22 UTCGHSA enrichment
  24. 2026-10-01 19:51 UTCEPSS rescore
  25. 2026-10-01 17:01 UTCVendor advisory
Show 41 more
  1. 2026-10-01 17:01 UTCGHSA enrichment
  2. 2026-10-01 05:33 UTCVendor advisory
  3. 2026-10-01 05:33 UTCGHSA enrichment
  4. 2026-09-30 18:14 UTCEG score recompute
  5. 2026-09-30 18:14 UTCGHSA enrichment
  6. 2026-09-30 15:04 UTCEPSS rescore
  7. 2026-09-30 06:52 UTCVendor advisory
  8. 2026-09-30 06:52 UTCGHSA enrichment
  9. 2026-09-29 19:32 UTCEG score recompute
  10. 2026-09-29 19:32 UTCVendor advisory
  11. 2026-09-29 19:32 UTCGHSA enrichment
  12. 2026-09-29 08:11 UTCEG score recompute
  13. 2026-09-29 08:11 UTCVendor advisory
  14. 2026-09-29 08:11 UTCGHSA enrichment
  15. 2026-09-28 20:49 UTCEG score recompute
  16. 2026-09-28 20:49 UTCVendor advisory
  17. 2026-09-28 20:49 UTCGHSA enrichment
  18. 2026-09-28 13:52 UTCEPSS rescore
  19. 2026-09-28 13:52 UTCEPSS rescore
  20. 2026-09-28 09:29 UTCVendor advisory
  21. 2026-09-28 09:29 UTCGHSA enrichment
  22. 2026-09-27 22:09 UTCEG score recompute
  23. 2026-09-27 22:08 UTCGHSA enrichment
  24. 2026-09-27 13:49 UTCEPSS rescore
  25. 2026-09-27 10:48 UTCGHSA enrichment
  26. 2026-09-26 23:28 UTCEG score recompute
  27. 2026-09-26 23:28 UTCGHSA enrichment
  28. 2026-09-26 15:59 UTCEPSS rescore
  29. 2026-09-26 12:03 UTCGHSA enrichment
  30. 2026-09-26 00:44 UTCEG score recompute
  31. 2026-09-26 00:43 UTCGHSA enrichment
  32. 2026-09-25 13:21 UTCEG score recompute
  33. 2026-09-25 13:21 UTCGHSA enrichment
  34. 2026-09-25 12:54 UTCEG score recompute
  35. 2026-09-25 12:54 UTCGHSA enrichment
  36. 2026-09-25 05:17 UTCEG score recompute▲ 7.70
  37. 2026-09-25 05:17 UTCGHSA enrichment
  38. 2026-09-25 05:16 UTCMITRE cvelistV5CVSS v3 → 7.7 · severity → HIGH
  39. 2026-09-24 17:33 UTCNVD update
  40. 2026-09-24 16:28 UTCEG score recompute
  41. 2026-09-24 16:26 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-97445?
CVE-2026-97445 is a high vulnerability published on September 24, 2026. In the Linux kernel, the following vulnerability has been resolved: ACPICA: Enhance buffer validation in acpiutwalkamlresources() Enhance buffer validation in acpiutwalkamlresources() to prevent buffer overflows.
When was CVE-2026-97445 disclosed?
CVE-2026-97445 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-97445 actively exploited?
CVE-2026-97445 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (4th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-97445?
CVE-2026-97445 has a CVSS base score of 7.7 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-97445?
No fix for CVE-2026-97445 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-97445 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-97445

Explore →

Is Your Infrastructure Affected by CVE-2026-97445?

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

Book a Demo →Browse All CVEs