CVE-2026-90173

CRITICALPre-NVD 9.89.8—
EchelonGraph scoreHIGH confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 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.6%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:

smb: smbdirect: free completion queues with ib_free_cq()

smbdirect_connection_destroy_qp() creates the send and receive completion queues with ib_alloc_cq_any(), which for IB_POLL_WORKQUEUE arms an internal completion handler that runs ib_cq_poll_work() on a workqueue. Tearing those CQs down with ib_destroy_cq() frees them without first cancelling that poll work.

If the provider posts a completion late -- for example Soft-RoCE (rxe) posting an RNR error from rxe_receiver() after rdma_destroy_qp() -- the handler re-queues ib_cq_poll_work() on the already-freed CQ, and a follow-on access faults in rxe_req_notify_cq().

Use ib_free_cq(), which cancel_work_sync()es the poll work before freeing the CQ, so no completion handler can run against a freed queue.

[ 1236.599526] ================================================================== [ 1236.602142] BUG: KASAN: slab-use-after-free in ib_cq_poll_work+0xd0/0x1a0 [ 1236.605524] Read of size 8 at addr ffff888111865800 by task kworker/4:1H/82 [ 1236.609017] [ 1236.609270] CPU: 4 UID: 0 PID: 82 Comm: kworker/4:1H Not tainted 7.2.0-rc3-next-20260717-virtme #110 PREEMPT(lazy) [ 1236.609287] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.17.0-debian-1.17.0-1 04/01/2014 [ 1236.609498] Workqueue: ib-comp-wq ib_cq_poll_work [ 1236.609525] Call Trace: [ 1236.609536] [ 1236.609545] __dump_stack+0x21/0x60 [ 1236.609562] dump_stack_lvl+0xc2/0x100 [ 1236.609573] print_address_description+0x77/0x200 [ 1236.609587] ? ib_cq_poll_work+0xd0/0x1a0 [ 1236.609597] print_report+0x58/0x70 [ 1236.609607] kasan_report+0x117/0x150 [ 1236.609623] ? ib_cq_poll_work+0xd0/0x1a0 [ 1236.609636] ? process_scheduled_works+0x954/0x1600 [ 1236.609650] ib_cq_poll_work+0xd0/0x1a0 [ 1236.609662] ? process_scheduled_works+0x954/0x1600 [ 1236.609674] process_scheduled_works+0xc22/0x1600 [ 1236.609698] ? __pfx_process_scheduled_works+0x10/0x10 [ 1236.609713] ? __pfx_assign_work+0x10/0x10 [ 1236.609726] ? lock_is_held_type+0x7b/0x110 [ 1236.609741] worker_thread+0x975/0xee0 [ 1236.609757] ? __pfx_do_raw_spin_lock+0x10/0x10 [ 1236.609775] ? __kthread_parkme+0x21e/0x260 [ 1236.609789] kthread+0x3a6/0x490 [ 1236.609800] ? __pfx_worker_thread+0x10/0x10 [ 1236.609809] ? __pfx_kthread+0x10/0x10 [ 1236.609820] ret_from_fork+0x55a/0xa20 [ 1236.609835] ? __pfx_ret_from_fork+0x10/0x10 [ 1236.609850] ? __pfx_kthread+0x10/0x10 [ 1236.609861] ret_from_fork_asm+0x1a/0x30 [ 1236.609880] [ 1236.609886] [ 1236.661292] Allocated by task 5076: [ 1236.662640] kasan_save_track+0x3e/0x80 [ 1236.663842] __kasan_kmalloc+0x72/0x90 [ 1236.664763] __kmalloc_noprof+0x2b0/0x5d0 [ 1236.665356] __ib_alloc_cq+0x284/0x1000 [ 1236.666573] __ib_alloc_cq_any+0x23e/0x340 [ 1236.668654] smbdirect_connection_create_qp+0x6f7/0x1070 [ 1236.669757] smbdirect_accept_connect_request+0x500/0x1ca0 [ 1236.672625] smbdirect_listen_rdma_event_handler+0x1655/0x1c50 [ 1236.673930] cma_listen_handler+0x1bf/0x260 [ 1236.674923] cma_cm_event_handler+0x128/0x380 [ 1236.676926] cma_ib_req_handler+0x2d3d/0x4de0 [ 1236.678368] cm_process_work+0xb0/0x530 [ 1236.680454] cm_queue_work_unlock+0xb1/0x230 [ 1236.681673] cm_work_handler+0x969f/0xdca0 [ 1236.682704] process_scheduled_works+0xc22/0x1600 [ 1236.683447] worker_thread+0x975/0xee0 [ 1236.685901] kthread+0x3a6/0x490 [ 1236.688164] ret_from_fork+0x55a/0xa20 [ 1236.689522] ret_from_fork_asm+0x1a/0x30 [ 1236.690073] [ 1236.690378] Freed by task 5137: [ 1236.692242] kasan_save_track+0x3e/0x80 [ 1236.694272] kasan_save_free_info+0x40/0x50 [ 1236.695514] __kasan_slab_free+0x3a/0x60 [ 1236.696773] kfree+0x14e/0x4e0 [ 1236.697216] ib_destroy_cq_user+0x18d/0x250 [ 1236.699817] smbdirect_connection_destroy_qp+0xf2/0x280 [ 1236.702115] smbdirect_socket_destroy_sync+0x1607/0x2720 [ 1236.704062] smbdirect_socket_release+0x140/0x280 [ 1236.705286] smb_direct_free_transpor ---truncated---

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.6%
EPSS %ILE
44th
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 17, 2026

Last Modified

September 18, 2026

Advisory Details (2)

Auto-updated Oct 2, 2026
No patch confirmed yet.
generic

smb: smbdirect: free completion queues with ib_free_cq() - kernel/git/stable/linux.git - Linux kernel stable tree

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

smb: smbdirect: free completion queues with ib_free_cq() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/8a953b1a47fffb71e70767bc1e914401e3c2f27f

Vendor Advisories for CVE-2026-90173(1)

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

Affected Packages

(1 across 1 ecosystem)
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 7.2~rc7-1~exp1 (178 versions)
  • every version up to 7.2.6-1: fixed in 7.2.6-1
—

Data Freshness Timeline

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

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

Frequently asked(5)

What is CVE-2026-90173?
CVE-2026-90173 is a critical vulnerability published on September 17, 2026. In the Linux kernel, the following vulnerability has been resolved: smb: smbdirect: free completion queues with ibfreecq() smbdirectconnectiondestroy_qp() creates the send and receive completion queues with iballoccqany(), which for IBPOLL_WORKQUEUE arms an internal completion handler that runs…
When was CVE-2026-90173 disclosed?
CVE-2026-90173 was first published on September 17, 2026, with the most recent update on September 18, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-90173 actively exploited?
CVE-2026-90173 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.6% probability of exploitation in the next 30 days (44th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-90173?
CVE-2026-90173 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-90173?
No fix for CVE-2026-90173 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-90173 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-90173

Explore →

Is Your Infrastructure Affected by CVE-2026-90173?

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

Book a Demo →Browse All CVEs