CVE-2026-31557

HIGHNVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-04-24. NVD baseline CVSS 7.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
7.5EG
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.5Exploit: 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:

nvmet: move async event work off nvmet-wq

For target nvmet_ctrl_free() flushes ctrl->async_event_work. If nvmet_ctrl_free() runs on nvmet-wq, the flush re-enters workqueue completion for the same worker:-

A. Async event work queued on nvmet-wq (prior to disconnect): nvmet_execute_async_event() queue_work(nvmet_wq, &ctrl->async_event_work)

nvmet_add_async_event() queue_work(nvmet_wq, &ctrl->async_event_work)

B. Full pre-work chain (RDMA CM path): nvmet_rdma_cm_handler() nvmet_rdma_queue_disconnect() __nvmet_rdma_queue_disconnect() queue_work(nvmet_wq, &queue->release_work) process_one_work() lock((wq_completion)nvmet-wq) <--------- 1st nvmet_rdma_release_queue_work()

C. Recursive path (same worker): nvmet_rdma_release_queue_work() nvmet_rdma_free_queue() nvmet_sq_destroy() nvmet_ctrl_put() nvmet_ctrl_free() flush_work(&ctrl->async_event_work) __flush_work() touch_wq_lockdep_map() lock((wq_completion)nvmet-wq) <--------- 2nd

Lockdep splat:

============================================ WARNING: possible recursive locking detected 6.19.0-rc3nvme+ #14 Tainted: G N -------------------------------------------- kworker/u192:42/44933 is trying to acquire lock: ffff888118a00948 ((wq_completion)nvmet-wq){+.+.}-{0:0}, at: touch_wq_lockdep_map+0x26/0x90

but task is already holding lock: ffff888118a00948 ((wq_completion)nvmet-wq){+.+.}-{0:0}, at: process_one_work+0x53e/0x660

3 locks held by kworker/u192:42/44933: #0: ffff888118a00948 ((wq_completion)nvmet-wq){+.+.}-{0:0}, at: process_one_work+0x53e/0x660 #1: ffffc9000e6cbe28 ((work_completion)(&queue->release_work)){+.+.}-{0:0}, at: process_one_work+0x1c5/0x660 #2: ffffffff82d4db60 (rcu_read_lock){....}-{1:3}, at: __flush_work+0x62/0x530

Workqueue: nvmet-wq nvmet_rdma_release_queue_work [nvmet_rdma] Call Trace: __flush_work+0x268/0x530 nvmet_ctrl_free+0x140/0x310 [nvmet] nvmet_cq_put+0x74/0x90 [nvmet] nvmet_rdma_free_queue+0x23/0xe0 [nvmet_rdma] nvmet_rdma_release_queue_work+0x19/0x50 [nvmet_rdma] process_one_work+0x206/0x660 worker_thread+0x184/0x320 kthread+0x10c/0x240 ret_from_fork+0x319/0x390

Move async event work to a dedicated nvmet-aen-wq to avoid reentrant flush on nvmet-wq.

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

Published

April 24, 2026

Last Modified

August 5, 2026

Advisory Details (4)

Auto-updated Jun 6, 2026
No patch confirmed yet.
generic

nvmet: move async event work off nvmet-wq - kernel/git/stable/linux.git - Linux kernel stable tree

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

nvmet: move async event work off nvmet-wq - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/49c7c50ee6325a084216e94395e067ecde8088fa
generic

nvmet: move async event work off nvmet-wq - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/2922e3507f6d5caa7f1d07f145e186fc6f317a4e
generic

nvmet: move async event work off nvmet-wq - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/25ceffc1dabec3b93f458b437aae26f4da293f87

Vendor Advisories for CVE-2026-31557(1)

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

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
linuxKernel @ 6.12.80—osv

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

(3 across 3 ecosystems)
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 7.2~rc7-1~exp1 (350 versions)——
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 (124 versions)6.19.11-1—

All Vendor Advisories

(13)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 5× in last 7d / 32× 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 239 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-31557?
CVE-2026-31557 is a high vulnerability published on April 24, 2026. In the Linux kernel, the following vulnerability has been resolved: nvmet: move async event work off nvmet-wq For target nvmetctrlfree() flushes ctrl->asynceventwork. If nvmetctrlfree() runs on nvmet-wq, the flush re-enters workqueue completion for the same worker:- A. Async event work queued on…
When was CVE-2026-31557 disclosed?
CVE-2026-31557 was first published in the National Vulnerability Database on April 24, 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-31557 actively exploited?
CVE-2026-31557 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 62.8% of all scored CVEs.
What is the CVSS score of CVE-2026-31557?
CVE-2026-31557 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-31557?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-31557, 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-31557

Explore →

Is Your Infrastructure Affected by CVE-2026-31557?

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

Start Free Scan →Browse All CVEs