CVE-2026-31426

HIGHNVD 7.07.0—
EchelonGraph scoreMEDIUM confidence

Score 7.0 from GitHub Security Advisory (severity: HIGH) published 2026-04-13. NVD baseline CVSS 7.0; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
7.0EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.0Exploit: None knownExposed: 0

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

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

ACPI: EC: clean up handlers on probe failure in acpi_ec_setup()

When ec_install_handlers() returns -EPROBE_DEFER on reduced-hardware platforms, it has already started the EC and installed the address space handler with the struct acpi_ec pointer as handler context. However, acpi_ec_setup() propagates the error without any cleanup.

The caller acpi_ec_add() then frees the struct acpi_ec for non-boot instances, leaving a dangling handler context in ACPICA.

Any subsequent AML evaluation that accesses an EC OpRegion field dispatches into acpi_ec_space_handler() with the freed pointer, causing a use-after-free:

BUG: KASAN: slab-use-after-free in mutex_lock (kernel/locking/mutex.c:289) Write of size 8 at addr ffff88800721de38 by task init/1 Call Trace: mutex_lock (kernel/locking/mutex.c:289) acpi_ec_space_handler (drivers/acpi/ec.c:1362) acpi_ev_address_space_dispatch (drivers/acpi/acpica/evregion.c:293) acpi_ex_access_region (drivers/acpi/acpica/exfldio.c:246) acpi_ex_field_datum_io (drivers/acpi/acpica/exfldio.c:509) acpi_ex_extract_from_field (drivers/acpi/acpica/exfldio.c:700) acpi_ex_read_data_from_field (drivers/acpi/acpica/exfield.c:327) acpi_ex_resolve_node_to_value (drivers/acpi/acpica/exresolv.c:392)

Allocated by task 1: acpi_ec_alloc (drivers/acpi/ec.c:1424) acpi_ec_add (drivers/acpi/ec.c:1692)

Freed by task 1: kfree (mm/slub.c:6876) acpi_ec_add (drivers/acpi/ec.c:1751)

The bug triggers on reduced-hardware EC platforms (ec->gpe < 0) when the GPIO IRQ provider defers probing. Once the stale handler exists, any unprivileged sysfs read that causes AML to touch an EC OpRegion (battery, thermal, backlight) exercises the dangling pointer.

Fix this by calling ec_remove_handlers() in the error path of acpi_ec_setup() before clearing first_ec. ec_remove_handlers() checks each EC_FLAGS_* bit before acting, so it is safe to call regardless of how far ec_install_handlers() progressed:

-ENODEV (handler not installed): only calls acpi_ec_stop() -EPROBE_DEFER (handler installed): removes handler, stops EC

CVSS v3
7.0
EG Score
7.0(medium)
EG Risk
36(Track)
EG Risk 36/100SSVC: Track

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
Severity70% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
1%
KEV
Not listed

Published

April 13, 2026

Last Modified

August 5, 2026

Advisory Details (6)

Auto-updated Aug 2, 2026
No patch confirmed yet.
generic

ACPI: EC: clean up handlers on probe failure in acpi_ec_setup() - kernel/git/stable/linux.git - Linux kernel stable tree

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

ACPI: EC: clean up handlers on probe failure in acpi_ec_setup() - kernel/git/stable/linux.git - Linux kernel stable tree

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

ACPI: EC: clean up handlers on probe failure in acpi_ec_setup() - kernel/git/stable/linux.git - Linux kernel stable tree

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

ACPI: EC: clean up handlers on probe failure in acpi_ec_setup() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/9c886e63b69658959633937e3acb7ca8addf7499
generic

ACPI: EC: clean up handlers on probe failure in acpi_ec_setup() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/808c0f156f48d5b8ca34088cbbfba8444e606cbc
generic

ACPI: EC: clean up handlers on probe failure in acpi_ec_setup() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/022d1727f33ff90b3e1775125264e3023901952e

Vendor Advisories for CVE-2026-31426(2)

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

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
linuxKernel @ 6.1.168—osv

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(5 across 4 ecosystems)
Debian:11(2)
PackageVulnerable rangeFixed inDependents
linux5.10.103-1 ... 7.2~rc5-1~exp1 (496 versions)——
linux-6.16.1.106-3~deb11u1 ... 6.1.164-1~deb11u1 (16 versions)6.1.170-1~deb11u1—
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 6.1.99-1 (48 versions)6.1.170-1—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.85-1~bpo12+1 (17 versions)6.12.85-1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 6.19~rc8-1~exp1 (121 versions)6.19.11-1—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Additional Vendor Advisories

(13)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 5× 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.

Showing the most recent 100 of 209 total refreshes for this CVE.

  1. 2026-09-04 05:06 UTCEPSS rescore
  2. 2026-09-02 05:28 UTCOSV refresh
  3. 2026-09-01 13:53 UTCEPSS rescore
  4. 2026-08-30 19:17 UTCEPSS rescore
  5. 2026-08-30 01:22 UTCEPSS rescore
  6. 2026-08-28 21:41 UTCEPSS rescore
  7. 2026-08-27 14:25 UTCEPSS rescore
  8. 2026-08-26 14:46 UTCEPSS rescore
  9. 2026-08-25 13:49 UTCEPSS rescore
  10. 2026-08-24 14:17 UTCEPSS rescore
  11. 2026-08-23 00:19 UTCEPSS rescore
  12. 2026-08-20 22:55 UTCEPSS rescore
  13. 2026-08-20 22:55 UTCEPSS rescore
  14. 2026-08-19 17:03 UTCEPSS rescore
  15. 2026-08-18 13:48 UTCEPSS rescore
  16. 2026-08-17 13:47 UTCEPSS rescore
  17. 2026-08-16 14:56 UTCEPSS rescore
  18. 2026-08-16 06:55 UTCEG score recompute
  19. 2026-08-16 06:55 UTCVendor advisory
  20. 2026-08-16 06:55 UTCGHSA enrichment
  21. 2026-08-16 02:14 UTCEPSS rescore
  22. 2026-08-15 01:30 UTCEPSS rescore
  23. 2026-08-14 18:17 UTCVendor advisory
  24. 2026-08-14 18:17 UTCGHSA enrichment
  25. 2026-08-14 04:56 UTCEG score recompute
Show 75 more
  1. 2026-08-14 04:56 UTCVendor advisory
  2. 2026-08-14 04:56 UTCGHSA enrichment
  3. 2026-08-13 22:00 UTCEPSS rescore
  4. 2026-08-13 09:15 UTCVendor advisory
  5. 2026-08-13 09:15 UTCGHSA enrichment
  6. 2026-08-12 19:10 UTCEG score recompute
  7. 2026-08-12 19:10 UTCVendor advisory
  8. 2026-08-12 19:10 UTCGHSA enrichment
  9. 2026-08-12 13:50 UTCEPSS rescore
  10. 2026-08-11 19:17 UTCEG score recompute
  11. 2026-08-11 19:17 UTCVendor advisory
  12. 2026-08-11 19:17 UTCGHSA enrichment
  13. 2026-08-11 02:52 UTCEG score recompute
  14. 2026-08-11 02:52 UTCVendor advisory
  15. 2026-08-11 02:52 UTCGHSA enrichment
  16. 2026-08-11 00:00 UTCEPSS rescore
  17. 2026-08-10 03:56 UTCVendor advisory
  18. 2026-08-10 03:56 UTCGHSA enrichment
  19. 2026-08-09 16:08 UTCEG score recompute
  20. 2026-08-09 16:08 UTCVendor advisory
  21. 2026-08-09 16:08 UTCGHSA enrichment
  22. 2026-08-09 13:46 UTCEPSS rescore
  23. 2026-08-09 04:19 UTCEG score recompute
  24. 2026-08-09 04:19 UTCVendor advisory
  25. 2026-08-09 04:19 UTCGHSA enrichment
  26. 2026-08-08 16:37 UTCEPSS rescore
  27. 2026-08-08 01:46 UTCEG score recompute
  28. 2026-08-08 01:46 UTCVendor advisory
  29. 2026-08-08 01:46 UTCGHSA enrichment
  30. 2026-08-07 13:58 UTCEG score recompute
  31. 2026-08-07 13:58 UTCVendor advisory
  32. 2026-08-07 13:58 UTCGHSA enrichment
  33. 2026-08-06 13:46 UTCEPSS rescore
  34. 2026-08-06 12:31 UTCVendor advisory
  35. 2026-08-06 12:31 UTCGHSA enrichment
  36. 2026-08-06 00:28 UTCEG score recompute
  37. 2026-08-06 00:28 UTCVendor advisory
  38. 2026-08-06 00:28 UTCGHSA enrichment
  39. 2026-08-05 19:17 UTCEPSS rescore
  40. 2026-08-05 12:40 UTCEG score recompute
  41. 2026-08-05 12:40 UTCVendor advisory
  42. 2026-08-05 12:40 UTCGHSA enrichment
  43. 2026-08-04 15:10 UTCEPSS rescore
  44. 2026-08-04 10:38 UTCEPSS rescore
  45. 2026-08-03 21:49 UTCEG score recompute
  46. 2026-08-03 21:49 UTCVendor advisory
  47. 2026-08-03 21:49 UTCGHSA enrichment
  48. 2026-08-03 10:36 UTCEPSS rescore
  49. 2026-08-03 01:23 UTCVendor advisory
  50. 2026-08-03 01:23 UTCGHSA enrichment
  51. 2026-08-02 13:34 UTCEG score recompute
  52. 2026-08-02 13:34 UTCVendor advisory
  53. 2026-08-02 13:34 UTCGHSA enrichment
  54. 2026-08-01 04:16 UTCEPSS rescore
  55. 2026-07-30 16:27 UTCEPSS rescore
  56. 2026-07-30 01:30 UTCEPSS rescore
  57. 2026-07-28 15:36 UTCEPSS rescore
  58. 2026-07-25 14:18 UTCEPSS rescore
  59. 2026-07-25 14:17 UTCEPSS rescore
  60. 2026-07-24 14:17 UTCEPSS rescore
  61. 2026-07-23 14:18 UTCEPSS rescore
  62. 2026-07-23 14:18 UTCEPSS rescore
  63. 2026-07-23 03:08 UTCEG score recompute
  64. 2026-07-22 14:08 UTCEPSS rescore
  65. 2026-07-22 14:08 UTCEPSS rescore
  66. 2026-07-21 15:24 UTCEPSS rescore
  67. 2026-07-21 15:24 UTCEPSS rescore
  68. 2026-07-20 17:08 UTCEPSS rescore
  69. 2026-07-20 17:08 UTCEPSS rescore
  70. 2026-07-20 12:02 UTCOSV refresh
  71. 2026-07-19 14:31 UTCEPSS rescore
  72. 2026-07-19 14:31 UTCEPSS rescore
  73. 2026-07-16 17:03 UTCEPSS rescore
  74. 2026-07-16 17:03 UTCEPSS rescore
  75. 2026-07-15 16:57 UTCEPSS rescore

Frequently asked(5)

What is CVE-2026-31426?
CVE-2026-31426 is a high vulnerability published on April 13, 2026. In the Linux kernel, the following vulnerability has been resolved: ACPI: EC: clean up handlers on probe failure in acpiecsetup() When ecinstallhandlers() returns -EPROBE_DEFER on reduced-hardware platforms, it has already started the EC and installed the address space handler with the struct…
When was CVE-2026-31426 disclosed?
CVE-2026-31426 was first published in the National Vulnerability Database on April 13, 2026, with the most recent update on August 5, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-31426 actively exploited?
CVE-2026-31426 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 98.6% of all scored CVEs.
What is the CVSS score of CVE-2026-31426?
CVE-2026-31426 has a CVSS v3 base score of 7.0 (NVD).
How do I remediate CVE-2026-31426?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-31426, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-31426?

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

Start Free Scan →Browse All CVEs