CVE-2026-97409

HIGHPre-NVD 8.88.8—
EchelonGraph scoreHIGH confidence

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

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

nvme-fc: Do not cancel requests in io target before it is initialized

A new nvme-fc controller in CONNECTING state sees admin request timeout schedules ctrl->ioerr_work to abort inflight requests. This ends up calling __nvme_fc_abort_outstanding_ios() which aborts requests in both admin and io tagsets. In case fc_ctrl->tag_set was not initialized we see the warning below. This is because ctrl.queue_count is initialized early in nvme_fc_alloc_ctrl().

nvme nvme0: NVME-FC{0}: starting error recovery Connectivity Loss INFO: trying to register non-static key. The code is fine but needs lockdep annotation, or maybe lpfc 0000:ab:00.0: queue 0 connect admin queue failed (-6). you didn't initialize this object before use? turning off the locking correctness validator. Workqueue: nvme-reset-wq nvme_fc_ctrl_ioerr_work [nvme_fc] Call Trace: dump_stack_lvl+0x57/0x80 register_lock_class+0x567/0x580 __lock_acquire+0x330/0xb90 lock_acquire.part.0+0xad/0x210 blk_mq_tagset_busy_iter+0xf9/0xc00 __nvme_fc_abort_outstanding_ios+0x23f/0x320 [nvme_fc] nvme_fc_ctrl_ioerr_work+0x172/0x210 [nvme_fc] process_one_work+0x82c/0x1450 worker_thread+0x5ee/0xfd0 kthread+0x3a0/0x750 ret_from_fork+0x439/0x670 ret_from_fork_asm+0x1a/0x30

Update the check in __nvme_fc_abort_outstanding_ios() confirm that io tagset was created before iterating over busy requests. Also make sure to cancel ctrl->ioerr_work before removing io tagset.

CVSS v3
8.8
EG Score
8.8HIGHhigh confidence
EG Risk
44
EG Risk 44/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
Severity88% × 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
13th
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

nvme-fc: Do not cancel requests in io target before it is initialized - kernel/git/stable/linux.git - Linux kernel stable tree

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

nvme-fc: Do not cancel requests in io target before it is initialized - kernel/git/stable/linux.git - Linux kernel stable tree

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

nvme-fc: Do not cancel requests in io target before it is initialized - kernel/git/stable/linux.git - Linux kernel stable tree

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

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

Frequently asked(5)

What is CVE-2026-97409?
CVE-2026-97409 is a high vulnerability published on September 24, 2026. In the Linux kernel, the following vulnerability has been resolved: nvme-fc: Do not cancel requests in io target before it is initialized A new nvme-fc controller in CONNECTING state sees admin request timeout schedules ctrl->ioerr_work to abort inflight requests. This ends up calling…
When was CVE-2026-97409 disclosed?
CVE-2026-97409 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-97409 actively exploited?
CVE-2026-97409 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (13th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-97409?
CVE-2026-97409 has a CVSS base score of 8.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-97409?
No fix for CVE-2026-97409 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-97409 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-97409

Explore →

Is Your Infrastructure Affected by CVE-2026-97409?

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

Book a Demo →Browse All CVEs