CVE-2026-93107

HIGHPre-NVD 8.28.2—
EchelonGraph scoreHIGH confidence

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

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

RDMA/rxe: Avoid reprocessing the current packet after the QP enters the error state

When do_complete() finds the QP in the error state it returns RESPST_CHK_RESOURCE. Before commit 49dc9c1f0c7e ("RDMA/rxe: Cleanup reset state handling in rxe_resp.c") this was the flush loop: check_resource() had an error-state branch that fetched each remaining recv WQE and completed it with IB_WC_WR_FLUSH_ERR, without touching the current packet. That commit removed the error-state branch from check_resource() (draining is now done at rxe_receiver() entry) but kept the do_complete() error-state return.

As a result, when a QP moves to the error state while a packet is being completed - e.g. an rdma_cm disconnect racing with receive processing - the responder state machine loops back into the request processing chain with the already-completed packet still in hand: check_resource() fetches a fresh recv WQE, execute()/send_data_in() copies the same packet payload again, do_complete() posts another IB_WC_SUCCESS CQE (qp->resp.status is still 0), and control returns to the error-state check. The loop re-executes the same packet once per posted recv WQE (observed: ~1000 duplicate IB_WC_SUCCESS completions of one SEND, one per ~8us, matching the RQ occupancy) until the RQ is exhausted, after which qp->resp.wqe is NULL and send_data_in() dereferences it:

BUG: kernel NULL pointer dereference, address: 0000000000000014 Workqueue: rxe_wq do_work RIP: copy_data+0x29/0x1f0 Call Trace: send_data_in+0x25/0x50 rxe_receiver+0xf36/0x1dd0

The duplicate completions are indistinguishable from real receives to the ULP. During an rds stress test, the message was accepted as new and delivered the same datagram to user space hundreds of times, corrupting the stream; any ULP that relies on RC exactly-once delivery is affected.

A live packet reaching the error-state check in do_complete() has been executed and completed exactly once and must be consumed, not re-processed. Return RESPST_CLEANUP for it (dequeue and free); keep returning RESPST_CHK_RESOURCE for the pkt == NULL case.

CVSS v3
8.2
EG Score
8.2HIGHhigh confidence
EG Risk
42
EG Risk 42/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
Severity82% × 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 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 (5)

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

RDMA/rxe: Avoid reprocessing the current packet after the QP enters the error state - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/15ae32c4a3551c4c9da457370bdfdd65d171e512
generic

RDMA/rxe: Avoid reprocessing the current packet after the QP enters the error state - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/0d37e2503efd1069a74be740eadf63ea17c96810
generic

RDMA/rxe: Avoid reprocessing the current packet after the QP enters the error state - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/399713f1f0eac641351c8ceaec0ab8244ddcf78c
generic

RDMA/rxe: Avoid reprocessing the current packet after the QP enters the error state - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/62a4b48767e06fdd64548450fae2b1ffc6ff5d69
generic

RDMA/rxe: Avoid reprocessing the current packet after the QP enters the error state - kernel/git/stable/linux.git - Linux kernel stable tree

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

Vendor Advisories for CVE-2026-93107(1)

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

Affected Packages

(3 across 3 ecosystems)
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
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 (179 versions)
  • every version up to 7.2.6-1: fixed in 7.2.6-1
—

Data Freshness Timeline

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

Frequently asked(5)

What is CVE-2026-93107?
CVE-2026-93107 is a high vulnerability published on September 17, 2026. In the Linux kernel, the following vulnerability has been resolved: RDMA/rxe: Avoid reprocessing the current packet after the QP enters the error state When do_complete() finds the QP in the error state it returns RESPSTCHKRESOURCE. Before commit 49dc9c1f0c7e ("RDMA/rxe: Cleanup reset state…
When was CVE-2026-93107 disclosed?
CVE-2026-93107 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-93107 actively exploited?
CVE-2026-93107 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-93107?
CVE-2026-93107 has a CVSS base score of 8.2 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-93107?
No fix for CVE-2026-93107 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-93107 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-93107

Explore →

Is Your Infrastructure Affected by CVE-2026-93107?

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