CVE-2026-90172

HIGHPre-NVD 7.57.5—
EchelonGraph scoreHIGH confidence

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

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

smb: smbdirect: destroy QP before mem pools on accept failure

On the rdma_accept_failed error path of smbdirect_accept_connect_request(), the receive io posted just above is owned by the QP (recv_io is set to NULL after a successful post). The error path fell through to smbdirect_connection_destroy_mem_pools() before smbdirect_connection_destroy_qp(), so the mem pools and the recv_io slab cache were destroyed while that recv_io was still outstanding on the QP.

The drain in smbdirect_connection_destroy_qp() (ib_drain_qp()) is what runs the recv completion that returns the recv_io to the free list, so destroying the pools first leaves the object outstanding at kmem_cache_destroy() time ("Slab cache still has objects") and later frees it into an already-destroyed mempool (mempool_free_bulk NULL-pointer dereference).

Give rdma_accept_failed its own teardown that drains the QP first, then destroys the mem pools, and returns. The remaining labels (post_recv_io_failed onward) run before the recv_io was ever posted, so they keep the mem-pools-then-qp order.

The outstanding recv_io at kmem_cache_destroy() time:

[ 3487.344647] ============================================================================= [ 3487.349942] BUG smbdirect_recv_io_cache_ffff88811ba99000 (Not tainted): Objects remaining on __kmem_cache_shutdown() [ 3487.356078] ----------------------------------------------------------------------------- [ 3487.356078] [ 3487.356738] Object 0xffff8881511c3440 @offset=13376 [ 3487.358464] Allocated in mempool_alloc_noprof+0x18c/0x290 age=1194 cpu=6 pid=22254 [ 3487.361197] mempool_alloc_noprof+0x18c/0x290 [ 3487.361542] smbdirect_connection_create_mem_pools+0x405/0x780 [ 3487.361972] smbdirect_accept_connect_request+0x5a8/0x1b80 [ 3487.362359] smbdirect_listen_rdma_event_handler+0x1579/0x1b90 [ 3487.362779] cma_cm_event_handler+0x9c/0x230 [ 3487.363096] cma_ib_req_handler+0x2682/0x45d0 [ 3487.363414] cm_process_work+0x56/0x3d0 [ 3487.363676] cm_work_handler+0x8a0e/0xd000 [ 3487.367496] process_scheduled_works+0xa07/0x13a0 [ 3487.367859] worker_thread+0x7c9/0xc80 [ 3487.368148] kthread+0x341/0x430 [ 3487.368407] ret_from_fork+0x3a8/0x7a0 [ 3487.368704] ret_from_fork_asm+0x1a/0x30 [ 3487.370307] Slab 0xffffea0005447000 objects=19 used=1 fp=0xffff8881511c0040 flags=0x100000000000240(workingset|head|node=0|zone=2) [ 3487.372840] ------------[ cut here ]------------ [ 3487.373195] WARNING: mm/slub.c:1244 at __slab_err+0x1a/0x30, CPU#6: kworker/6:84/22254 [ 3487.373759] Modules linked in: [ 3487.373993] CPU: 6 UID: 0 PID: 22254 Comm: kworker/6:84 Tainted: G B 7.1.0-next-20260623+ #88 PREEMPT(lazy) [ 3487.374778] Tainted: [B]=BAD_PAGE [ 3487.377830] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.17.0-debian-1.17.0-1 04/01/2014 [ 3487.378515] Workqueue: ib_cm cm_work_handler [ 3487.378820] RIP: 0010:__slab_err+0x1a/0x30 [ 3487.379129] Code: 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 0f 1f 44 00 00 e8 36 00 00 00 bf 05 00 00 00 be 01 00 00 00 e8 f7 75 45 00 90 <0f> 0b 90 c3 cc cc cc cc cc 66 66 66 66 2e 0f 1f 84 00 00 00 00 00 [ 3487.383255] RSP: 0018:ffff888220fc7050 EFLAGS: 00010093 [ 3487.383643] RAX: ffffffff8168e60a RBX: ffff88810955e640 RCX: ffff88821c381d80 [ 3487.384158] RDX: 0000000000000000 RSI: 0000000000000008 RDI: ffffffff870fa080 [ 3487.384662] RBP: ffff888220fc7068 R08: ffffffff870fa087 R09: 1ffffffff0e1f410 [ 3487.385192] R10: dffffc0000000000 R11: fffffbfff0e1f411 R12: ffffea0005447210 [ 3487.385674] R13: ffffea0005447000 R14: ffff888220fc7068 R15: ffff88812a8ab300 [ 3487.388932] FS: 0000000000000000(0000) GS:ffff888427e76000(0000) knlGS:0000000000000000 [ 3487.389529] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 3487.389934] CR2: 00007ffcf2d84fd8 CR3: 0000000111d64006 CR4: 0000000000f72ef0 [ 3487.390440] PKRU: 55555554 [ 3487.390641] Call Trace: [ 3487.390826] [ 3 ---truncated---

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

Last Modified

September 18, 2026

Advisory Details (2)

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

smb: smbdirect: destroy QP before mem pools on accept failure - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/959813a3752b459ed77b0b3eaf30b9f4c6204260
generic

smb: smbdirect: destroy QP before mem pools on accept failure - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/383a9480f5f40bc46454cce27ccfad532cedad9c

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

Frequently asked(5)

What is CVE-2026-90172?
CVE-2026-90172 is a high vulnerability published on September 17, 2026. In the Linux kernel, the following vulnerability has been resolved: smb: smbdirect: destroy QP before mem pools on accept failure On the rdmaacceptfailed error path of smbdirectacceptconnect_request(), the receive io posted just above is owned by the QP (recv_io is set to NULL after a successful…
When was CVE-2026-90172 disclosed?
CVE-2026-90172 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-90172 actively exploited?
CVE-2026-90172 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (39th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-90172?
CVE-2026-90172 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-90172?
No fix for CVE-2026-90172 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-90172 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-90172

Explore →

Is Your Infrastructure Affected by CVE-2026-90172?

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

Book a Demo →Browse All CVEs