CVE-2026-80589

CRITICALPre-NVD 9.89.8—
EchelonGraph scoreHIGH confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 5 sources updated this week
9.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: 9.8Exploit: 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:

block: stop the timeout timer when releasing a never added disk

disk_release() undoes blk_mq_init_allocated_queue() for a disk whose probe failed before add_disk(), but it only calls blk_mq_exit_queue(). Nothing there stops q->timeout, and that timer rolls forward: it stays pending until it next expires, not until the last request completes. So if the driver issued any I/O before adding the disk, the request_queue is freed while still linked into a timer wheel bucket.

Commit 6f8191fdf41d ("block: simplify disk shutdown") dropped the blk_cleanup_queue() call that used to stop it. __del_gendisk() and blk_mq_destroy_queue() still do; only the probe failure path lost it.

nvme gets there because nvme_update_ns_info() submits Report Zones or FDP io-mgmt-recv on ns->queue before the disk is added, so a later failure - a concurrent reset setting NVME_CTRL_FROZEN, or device_add_disk() failing - lands in put_disk() with the timer armed:

BUG: KASAN: slab-use-after-free in detach_if_pending+0x30c/0x340 Write of size 8 at addr ffff888004d71310 by task kworker/u8:2/37 __timer_delete_sync+0x156/0x240 kernel/time/timer.c:1621 blk_sync_queue+0x22/0x40 block/blk-core.c:222 nvme_sync_queues+0x100/0x150 drivers/nvme/host/core.c:5362 nvme_reset_work+0x138/0x930 drivers/nvme/host/pci.c:3264

Allocated by task 34: __blk_mq_alloc_disk+0x33/0x100 block/blk-mq.c:4462 nvme_alloc_ns+0x290/0x3870 drivers/nvme/host/core.c:4146

Freed by task 0: blk_free_queue_rcu+0x3a/0x50 block/blk-core.c:254 rcu_core+0xc10/0x1730 kernel/rcu/tree.c:2857

The queue being synced there is ctrl->admin_q, only a victim sharing a timer wheel bucket with the freed queue's dangling entry; other runs tripped in enqueue_timer(), __run_timers() or blk_mq_timeout_work(). Failing nvme_alloc_ns() with a debug patch makes it deterministic: one leaked timer trips KASAN within seconds, while 1987 patched releases produced no splat.

Stop the timer and the queue work items before blk_mq_exit_queue(), like blk_mq_destroy_queue() does.

Found by FuzzNvme.

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

Published

August 26, 2026

Last Modified

August 27, 2026

Advisory Details (6)

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

block: stop the timeout timer when releasing a never added disk - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/26cb8ebbfaf713c82e142d08828d4d765057633b
generic

block: stop the timeout timer when releasing a never added disk - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/93d620519d71dfc6ee64b5baea74f1d85d4439fb
generic

block: stop the timeout timer when releasing a never added disk - kernel/git/stable/linux.git - Linux kernel stable tree

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

block: stop the timeout timer when releasing a never added disk - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/1a0ae4d502062a2759f2a92d12bdeab3c64c7372
generic

block: stop the timeout timer when releasing a never added disk - kernel/git/stable/linux.git - Linux kernel stable tree

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

block: stop the timeout timer when releasing a never added disk - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/6ae7364f68e6c7af6b6df4bbb14040b89e5975d0

Vendor Advisories for CVE-2026-80589(1)

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

Data Freshness Timeline

(refreshed 37× in last 7d / 37× 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-08-31 04:53 UTCGHSA enrichment
  2. 2026-08-31 00:29 UTCGHSA enrichment
  3. 2026-08-30 20:05 UTCEG score recompute
  4. 2026-08-30 20:05 UTCGHSA enrichment
  5. 2026-08-30 19:18 UTCEPSS rescore
  6. 2026-08-30 19:17 UTCEPSS rescore
  7. 2026-08-30 15:42 UTCGHSA enrichment
  8. 2026-08-30 11:18 UTCGHSA enrichment
  9. 2026-08-30 06:54 UTCGHSA enrichment
  10. 2026-08-30 02:28 UTCEG score recompute
  11. 2026-08-30 02:28 UTCGHSA enrichment
  12. 2026-08-30 01:22 UTCEPSS rescore
  13. 2026-08-29 22:04 UTCGHSA enrichment
  14. 2026-08-29 17:41 UTCGHSA enrichment
  15. 2026-08-29 13:14 UTCGHSA enrichment
  16. 2026-08-29 08:49 UTCGHSA enrichment
  17. 2026-08-29 04:23 UTCGHSA enrichment
  18. 2026-08-28 23:57 UTCEG score recompute
  19. 2026-08-28 23:57 UTCGHSA enrichment
  20. 2026-08-28 21:42 UTCEPSS rescore
  21. 2026-08-28 18:05 UTCGHSA enrichment
  22. 2026-08-28 13:41 UTCGHSA enrichment
  23. 2026-08-28 09:14 UTCGHSA enrichment
  24. 2026-08-28 04:48 UTCGHSA enrichment
  25. 2026-08-28 00:23 UTCGHSA enrichment
Show 12 more
  1. 2026-08-27 19:55 UTCGHSA enrichment
  2. 2026-08-27 15:32 UTCEG score recompute
  3. 2026-08-27 15:31 UTCGHSA enrichment
  4. 2026-08-27 14:25 UTCEPSS rescore
  5. 2026-08-27 11:04 UTCGHSA enrichment
  6. 2026-08-27 06:39 UTCEG score recompute
  7. 2026-08-27 06:38 UTCGHSA enrichment
  8. 2026-08-27 06:17 UTCEG score recompute▲ 9.80
  9. 2026-08-27 06:11 UTCMITRE cvelistV5CVSS v3 → 9.8 · severity → CRITICAL
  10. 2026-08-26 15:43 UTCNVD update
  11. 2026-08-26 14:42 UTCEG score recompute
  12. 2026-08-26 14:41 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-80589?
CVE-2026-80589 is a critical vulnerability published on August 26, 2026. In the Linux kernel, the following vulnerability has been resolved: block: stop the timeout timer when releasing a never added disk diskrelease() undoes blkmqinitallocated_queue() for a disk whose probe failed before adddisk(), but it only calls blkmqexitqueue(). Nothing there stops q->timeout, and…
When was CVE-2026-80589 disclosed?
CVE-2026-80589 was first published in the National Vulnerability Database on August 26, 2026, with the most recent update on August 27, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-80589 actively exploited?
CVE-2026-80589 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 69.6% of all scored CVEs.
What is the CVSS score of CVE-2026-80589?
CVE-2026-80589 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2026-80589?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-80589, 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

Explore the affected products and dependency analysis for CVE-2026-80589

Explore →

Is Your Infrastructure Affected by CVE-2026-80589?

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

Start Free Scan →Browse All CVEs