CVE-2026-31389

HIGHPre-NVD 7.87.8
EchelonGraph scoreMEDIUM confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-04-03. the CNA's CVSS baseline 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cna:linux, epss, ghsa
7.8EG
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.8Exploit: None knownExposed: 0

A fix is available — apply it.

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

spi: fix use-after-free on controller registration failure

Make sure to deregister from driver core also in the unlikely event that per-cpu statistics allocation fails during controller registration to avoid use-after-free (of driver resources) and unclocked register accesses.

CVSS v3
7.8
EG Score
7.8(medium)
EG Risk
40(Track)
EG Risk 40/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
Severity78% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
2%
KEV
Not listed

Published

April 3, 2026

Last Modified

August 5, 2026

Advisory Details (6)

Auto-updated May 20, 2026
No patch confirmed yet.
generic

spi: fix use-after-free on controller registration failure - kernel/git/stable/linux.git - Linux kernel stable tree

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

spi: fix use-after-free on controller registration failure - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/8634e05b08ead636e926022f4a98416e13440df9
generic

spi: fix use-after-free on controller registration failure - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/80f3e8cd2b4ad355b2ad2024cf423f6d183404f7
generic

spi: fix use-after-free on controller registration failure - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/6bbd385b30c7fb6c7ee0669e9ada91490938c051
generic

spi: fix use-after-free on controller registration failure - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/23b51bad2eb8787aa74324cfccefb258515ae5ba
generic

spi: fix use-after-free on controller registration failure - kernel/git/stable/linux.git - Linux kernel stable tree

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

Vendor Advisories for CVE-2026-31389(1)

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

Patch Availability(11)

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

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
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 (119 versions)6.19.10-1

Weakness Classification(1)

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

All Vendor Advisories

(13)

Data Freshness Timeline

(refreshed 6× in last 7d / 59× 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 204 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-31389?
CVE-2026-31389 is a high vulnerability published on April 3, 2026. In the Linux kernel, the following vulnerability has been resolved: spi: fix use-after-free on controller registration failure Make sure to deregister from driver core also in the unlikely event that per-cpu statistics allocation fails during controller registration to avoid use-after-free (of…
When was CVE-2026-31389 disclosed?
CVE-2026-31389 was first published in the National Vulnerability Database on April 3, 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-31389 actively exploited?
CVE-2026-31389 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.2% of all scored CVEs.
What is the CVSS score of CVE-2026-31389?
CVE-2026-31389 has a CVSS v4.0 base score of 7.8 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-31389?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-31389, 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-31389

Explore →

Is Your Infrastructure Affected by CVE-2026-31389?

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