CVE-2026-68417

HIGHPre-NVD 7.87.8
EchelonGraph scoreHIGH confidence

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

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

RDMA/siw: publish QP after initialization

siw_create_qp() currently calls siw_qp_add() before the queues, CQ pointers, state, completion, and device list entry are ready. A QPN lookup can therefore reach a QP that is still being constructed.

Move siw_qp_add() to the end of siw_create_qp(), after QP initialization and before adding the QP to the siw device list.

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

Published

August 10, 2026

Last Modified

August 19, 2026

Advisory Details (5)

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

RDMA/siw: publish QP after initialization - kernel/git/stable/linux.git - Linux kernel stable tree

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

RDMA/siw: publish QP after initialization - kernel/git/stable/linux.git - Linux kernel stable tree

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

RDMA/siw: publish QP after initialization - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/74912ad168f87d6b2b670a87987bb302d6e64aa1
generic

RDMA/siw: publish QP after initialization - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/52f9fcb191143448df55fd215ff09c5207fed43e
generic

RDMA/siw: publish QP after initialization - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/36e91a58397ca8c978e38a0bf389f0c6113fa8ca

Vendor Advisories for CVE-2026-68417(2)

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 / 49× 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-21 05:21 UTCEG score recompute
  2. 2026-08-21 05:21 UTCVendor advisory
  3. 2026-08-21 05:21 UTCGHSA enrichment
  4. 2026-08-20 22:56 UTCEPSS rescore
  5. 2026-08-20 17:30 UTCGHSA enrichment
  6. 2026-08-20 05:40 UTCGHSA enrichment
  7. 2026-08-19 17:49 UTCEG score recompute
  8. 2026-08-19 17:49 UTCGHSA enrichment
  9. 2026-08-19 17:04 UTCEPSS rescore
  10. 2026-08-19 16:53 UTCEG score recompute
  11. 2026-08-19 16:53 UTCGHSA enrichment
  12. 2026-08-19 06:51 UTCGHSA enrichment
  13. 2026-08-18 19:01 UTCEG score recompute
  14. 2026-08-18 19:01 UTCGHSA enrichment
  15. 2026-08-18 13:49 UTCEPSS rescore
  16. 2026-08-18 13:49 UTCEPSS rescore
  17. 2026-08-18 07:10 UTCGHSA enrichment
  18. 2026-08-17 19:18 UTCEG score recompute
  19. 2026-08-17 19:18 UTCGHSA enrichment
  20. 2026-08-17 13:47 UTCEPSS rescore
  21. 2026-08-17 06:31 UTCEG score recompute
  22. 2026-08-17 06:31 UTCGHSA enrichment
  23. 2026-08-17 05:35 UTCEG score recompute
  24. 2026-08-17 05:35 UTCGHSA enrichment
  25. 2026-08-16 22:48 UTCEG score recompute
Show 24 more
  1. 2026-08-16 22:48 UTCGHSA enrichment
  2. 2026-08-16 14:56 UTCEPSS rescore
  3. 2026-08-16 14:56 UTCEPSS rescore
  4. 2026-08-16 10:57 UTCEG score recompute
  5. 2026-08-16 10:57 UTCGHSA enrichment
  6. 2026-08-15 23:07 UTCGHSA enrichment
  7. 2026-08-15 11:16 UTCEG score recompute
  8. 2026-08-15 11:16 UTCGHSA enrichment
  9. 2026-08-15 01:30 UTCEPSS rescore
  10. 2026-08-14 23:25 UTCGHSA enrichment
  11. 2026-08-14 11:34 UTCEG score recompute
  12. 2026-08-14 11:34 UTCGHSA enrichment
  13. 2026-08-13 23:44 UTCEG score recompute
  14. 2026-08-13 23:44 UTCGHSA enrichment
  15. 2026-08-13 23:03 UTCEG score recompute 7.80
  16. 2026-08-13 23:03 UTCGHSA enrichment
  17. 2026-08-13 23:03 UTCMITRE cvelistV5CVSS v3 → 7.8 · severity → HIGH
  18. 2026-08-13 22:00 UTCEPSS rescore
  19. 2026-08-13 11:47 UTCEG score recompute
  20. 2026-08-13 11:47 UTCGHSA enrichment
  21. 2026-08-12 13:51 UTCEPSS rescore
  22. 2026-08-10 13:24 UTCNVD update
  23. 2026-08-10 12:17 UTCEG score recompute
  24. 2026-08-10 12:17 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-68417?
CVE-2026-68417 is a high vulnerability published on August 10, 2026. In the Linux kernel, the following vulnerability has been resolved: RDMA/siw: publish QP after initialization siwcreateqp() currently calls siwqpadd() before the queues, CQ pointers, state, completion, and device list entry are ready. A QPN lookup can therefore reach a QP that is still being…
When was CVE-2026-68417 disclosed?
CVE-2026-68417 was first published in the National Vulnerability Database on August 10, 2026, with the most recent update on August 19, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-68417 actively exploited?
CVE-2026-68417 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 97.8% of all scored CVEs.
What is the CVSS score of CVE-2026-68417?
CVE-2026-68417 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-68417?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-68417, 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-68417

Explore →

Is Your Infrastructure Affected by CVE-2026-68417?

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