CVE-2026-98056

HIGHPre-NVD 7.57.5—
EchelonGraph scoreHIGH confidence

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

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

nvme_scan_ns_list() drops the stale namespaces in each gap in the reported NSID list one NSID at a time. Every iteration calls nvme_find_get_ns() to look the namespace up and removes it if it is present. The loop runs once per NSID in the gap rather than once per namespace actually present.

NSIDs are 32-bit, so a target with a sparse NSID space can make a single gap spin the loop billions of times with nothing to remove.

watchdog: BUG: soft lockup - CPU#4 stuck for 26s! Workqueue: nvme-wq nvme_scan_work [nvme_core] RIP: 0010:__srcu_read_unlock+0xb/0x20 Call Trace: nvme_find_get_ns+0x7d/0xb0 [nvme_core] nvme_scan_ns_list+0xe8/0x280 [nvme_core] nvme_scan_work+0x18a/0x280 [nvme_core] process_one_work+0x197/0x380 worker_thread+0x2fe/0x410 kthread+0xe0/0x100

Rename nvme_remove_invalid_namespaces() to nvme_remove_nsid_range() and give it an open (start, end) NSID range. ctrl->namespaces is sorted by NSID, so the whole gap is dropped in a single walk that stops once end is reached. This bounds the work by the namespaces that are present instead of by the size of the gap.

CVSS v3
7.5
EG Score
7.5HIGHhigh confidence
EG Risk
38
EG Risk 38/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
Severity75% × 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.6%
EPSS %ILE
47th
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 25, 2026

Last Modified

September 30, 2026

Advisory Details (4)

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

nvme: remove stale namespaces by NSID range during scan - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/4ed7f3d7d435bf5b63da2814dc9270f5ba896011
generic

nvme: remove stale namespaces by NSID range during scan - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/52200fc41a79da430ccf7c126ed837535b087ea2
generic

nvme: remove stale namespaces by NSID range during scan - kernel/git/stable/linux.git - Linux kernel stable tree

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

nvme: remove stale namespaces by NSID range during scan - kernel/git/stable/linux.git - Linux kernel stable tree

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

Vendor Advisories for CVE-2026-98056(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 (180 versions)
  • every version up to 7.2.7-1: fixed in 7.2.7-1
—

Data Freshness Timeline

(refreshed 43× in last 7d / 61× 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 04:59 UTCEG score recompute
  2. 2026-10-05 04:59 UTCVendor advisory
  3. 2026-10-05 04:59 UTCGHSA enrichment
  4. 2026-10-04 23:23 UTCEPSS rescore
  5. 2026-10-04 16:43 UTCVendor advisory
  6. 2026-10-04 16:43 UTCGHSA enrichment
  7. 2026-10-04 04:27 UTCVendor advisory
  8. 2026-10-04 04:27 UTCGHSA enrichment
  9. 2026-10-03 16:12 UTCEG score recompute
  10. 2026-10-03 16:12 UTCVendor advisory
  11. 2026-10-03 16:12 UTCGHSA enrichment
  12. 2026-10-03 14:26 UTCEPSS rescore
  13. 2026-10-03 03:56 UTCEG score recompute
  14. 2026-10-03 03:56 UTCVendor advisory
  15. 2026-10-03 03:56 UTCGHSA enrichment
  16. 2026-10-02 17:57 UTCEPSS rescore
  17. 2026-10-02 15:38 UTCVendor advisory
  18. 2026-10-02 15:38 UTCGHSA enrichment
  19. 2026-10-02 03:22 UTCEG score recompute
  20. 2026-10-02 03:22 UTCVendor advisory
  21. 2026-10-02 03:22 UTCGHSA enrichment
  22. 2026-10-01 19:51 UTCEPSS rescore
  23. 2026-10-01 15:06 UTCVendor advisory
  24. 2026-10-01 15:06 UTCGHSA enrichment
  25. 2026-10-01 02:50 UTCEG score recompute
Show 36 more
  1. 2026-10-01 02:50 UTCVendor advisory
  2. 2026-10-01 02:50 UTCGHSA enrichment
  3. 2026-09-30 15:04 UTCEPSS rescore
  4. 2026-09-30 14:35 UTCVendor advisory
  5. 2026-09-30 14:35 UTCGHSA enrichment
  6. 2026-09-30 06:30 UTCVendor advisory
  7. 2026-09-30 06:30 UTCGHSA enrichment
  8. 2026-09-29 18:14 UTCEG score recompute
  9. 2026-09-29 18:14 UTCVendor advisory
  10. 2026-09-29 18:14 UTCGHSA enrichment
  11. 2026-09-29 05:18 UTCEG score recompute
  12. 2026-09-29 05:18 UTCVendor advisory
  13. 2026-09-29 05:18 UTCGHSA enrichment
  14. 2026-09-28 17:03 UTCEG score recompute
  15. 2026-09-28 17:03 UTCVendor advisory
  16. 2026-09-28 17:03 UTCGHSA enrichment
  17. 2026-09-28 13:52 UTCEPSS rescore
  18. 2026-09-28 13:52 UTCEPSS rescore
  19. 2026-09-28 04:45 UTCGHSA enrichment
  20. 2026-09-27 16:28 UTCEG score recompute
  21. 2026-09-27 16:28 UTCGHSA enrichment
  22. 2026-09-27 13:49 UTCEPSS rescore
  23. 2026-09-27 04:13 UTCEG score recompute
  24. 2026-09-27 04:12 UTCGHSA enrichment
  25. 2026-09-26 15:59 UTCEPSS rescore
  26. 2026-09-26 15:56 UTCGHSA enrichment
  27. 2026-09-26 03:39 UTCEG score recompute
  28. 2026-09-26 03:39 UTCGHSA enrichment
  29. 2026-09-25 15:23 UTCEG score recompute
  30. 2026-09-25 15:23 UTCGHSA enrichment
  31. 2026-09-25 14:52 UTCEG score recompute▲ 7.50
  32. 2026-09-25 14:51 UTCGHSA enrichment
  33. 2026-09-25 14:49 UTCMITRE cvelistV5CVSS v3 → 7.5 · severity → HIGH
  34. 2026-09-25 11:30 UTCNVD update
  35. 2026-09-25 10:29 UTCEG score recompute
  36. 2026-09-25 10:27 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-98056?
CVE-2026-98056 is a high vulnerability published on September 25, 2026. In the Linux kernel, the following vulnerability has been resolved: nvme: remove stale namespaces by NSID range during scan nvmescanns_list() drops the stale namespaces in each gap in the reported NSID list one NSID at a time. Every iteration calls nvmefindget_ns() to look the namespace up and…
When was CVE-2026-98056 disclosed?
CVE-2026-98056 was first published on September 25, 2026, with the most recent update on September 30, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-98056 actively exploited?
CVE-2026-98056 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.6% probability of exploitation in the next 30 days (47th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-98056?
CVE-2026-98056 has a CVSS base score of 7.5 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-98056?
No fix for CVE-2026-98056 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-98056 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-98056

Explore →

Is Your Infrastructure Affected by CVE-2026-98056?

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

Book a Demo →Browse All CVEs