CVE-2026-89970

CRITICALPre-NVD 9.89.8—
EchelonGraph scoreHIGH confidence

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

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

nvmet-auth: Synchronize timeout work during SQ teardown

nvmet_auth_sq_free() cancels auth_expired_work with cancel_delayed_work(). If the work has already started, cancellation does not wait for the callback. Transport teardown can consequently free or reuse the queue containing struct nvmet_sq while nvmet_auth_expired_work() still accesses that SQ.

Add a teardown-specific helper that synchronously drains the delayed work before freeing authentication state, and use it from nvmet_sq_destroy(). Keep the non-synchronous helper for in-band authentication state cleanup, where the SQ owner remains alive.

CVSS v3
9.8
EG Score
9.8CRITICALhigh confidence
EG Risk
49
EG Risk 49/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
Severity98% × 45%
Exploitation1% × 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.8%
EPSS %ILE
56th
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 total (CVSS ≥ 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 16, 2026

Last Modified

September 16, 2026

Advisory Details (6)

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

nvmet-auth: Synchronize timeout work during SQ teardown - kernel/git/stable/linux.git - Linux kernel stable tree

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

nvmet-auth: Synchronize timeout work during SQ teardown - kernel/git/stable/linux.git - Linux kernel stable tree

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

nvmet-auth: Synchronize timeout work during SQ teardown - kernel/git/stable/linux.git - Linux kernel stable tree

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

nvmet-auth: Synchronize timeout work during SQ teardown - kernel/git/stable/linux.git - Linux kernel stable tree

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

nvmet-auth: Synchronize timeout work during SQ teardown - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/7555ddd60af72df2862dd8f9b730a9848577edda
generic

nvmet-auth: Synchronize timeout work during SQ teardown - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/664022fa1c93f4eba09ef5ee02411b9709dd7a93

Vendor Advisories for CVE-2026-89970(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 99× in last 7d / 278× 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 278 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-89970?
CVE-2026-89970 is a critical vulnerability published on September 16, 2026. In the Linux kernel, the following vulnerability has been resolved: nvmet-auth: Synchronize timeout work during SQ teardown nvmetauthsqfree() cancels authexpired_work with canceldelayedwork(). If the work has already started, cancellation does not wait for the callback. Transport teardown can…
When was CVE-2026-89970 disclosed?
CVE-2026-89970 was first published on September 16, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-89970 actively exploited?
CVE-2026-89970 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.8% probability of exploitation in the next 30 days (56th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-89970?
CVE-2026-89970 has a CVSS base score of 9.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-89970?
No fix for CVE-2026-89970 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-89970 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-89970

Explore →

Is Your Infrastructure Affected by CVE-2026-89970?

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