CVE-2026-68419

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 — 3 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/irdma: Prevent rereg_mr for non-mem regions

When a QP/CQ/SRQ is created, a two step process is used where the buffer is allocated in userspace and explicitly registered with the normal reg_mr mechanism prior to creating the actual QP/CQ/SRQ object.

These special registrations are indicated via an ABI field so the driver knows that they do not have a valid mkey and to skip the actual CQP command submission.

Since these are real MR objects from the core's perspective, it is possible for a user application to invoke rereg_mr on them and cause a real CQP op to be emitted with the zero-initialized mkey value of 0.

Fix this by preventing rereg_mr on these special regions.

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
3%
KEV
Not listed

Published

August 10, 2026

Last Modified

August 17, 2026

Advisory Details (5)

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

RDMA/irdma: Prevent rereg_mr for non-mem regions - kernel/git/stable/linux.git - Linux kernel stable tree

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

RDMA/irdma: Prevent rereg_mr for non-mem regions - kernel/git/stable/linux.git - Linux kernel stable tree

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

RDMA/irdma: Prevent rereg_mr for non-mem regions - kernel/git/stable/linux.git - Linux kernel stable tree

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

RDMA/irdma: Prevent rereg_mr for non-mem regions - kernel/git/stable/linux.git - Linux kernel stable tree

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

RDMA/irdma: Prevent rereg_mr for non-mem regions - kernel/git/stable/linux.git - Linux kernel stable tree

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

Vendor Advisories for CVE-2026-68419(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 33× in last 7d / 45× 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-20 22:56 UTCEPSS rescore
  2. 2026-08-20 22:51 UTCGHSA enrichment
  3. 2026-08-20 11:55 UTCGHSA enrichment
  4. 2026-08-20 00:54 UTCEG score recompute
  5. 2026-08-20 00:54 UTCGHSA enrichment
  6. 2026-08-19 17:04 UTCEPSS rescore
  7. 2026-08-19 13:56 UTCGHSA enrichment
  8. 2026-08-19 02:57 UTCGHSA enrichment
  9. 2026-08-18 15:37 UTCEG score recompute
  10. 2026-08-18 15:37 UTCGHSA enrichment
  11. 2026-08-18 13:49 UTCEPSS rescore
  12. 2026-08-18 13:49 UTCEPSS rescore
  13. 2026-08-18 04:24 UTCGHSA enrichment
  14. 2026-08-17 17:29 UTCEG score recompute
  15. 2026-08-17 13:47 UTCEPSS rescore
  16. 2026-08-17 06:31 UTCEG score recompute
  17. 2026-08-17 06:31 UTCGHSA enrichment
  18. 2026-08-17 05:35 UTCEG score recompute
  19. 2026-08-17 05:35 UTCGHSA enrichment
  20. 2026-08-17 04:15 UTCGHSA enrichment
  21. 2026-08-16 17:19 UTCEG score recompute
  22. 2026-08-16 17:19 UTCGHSA enrichment
  23. 2026-08-16 14:56 UTCEPSS rescore
  24. 2026-08-16 14:56 UTCEPSS rescore
  25. 2026-08-16 06:23 UTCEG score recompute
Show 20 more
  1. 2026-08-16 06:23 UTCGHSA enrichment
  2. 2026-08-15 19:28 UTCGHSA enrichment
  3. 2026-08-15 08:32 UTCEG score recompute
  4. 2026-08-15 08:32 UTCGHSA enrichment
  5. 2026-08-15 01:30 UTCEPSS rescore
  6. 2026-08-14 21:36 UTCGHSA enrichment
  7. 2026-08-14 10:40 UTCEG score recompute
  8. 2026-08-14 10:40 UTCGHSA enrichment
  9. 2026-08-13 23:44 UTCEG score recompute
  10. 2026-08-13 23:44 UTCGHSA enrichment
  11. 2026-08-13 23:03 UTCEG score recompute▲ 7.80
  12. 2026-08-13 23:03 UTCGHSA enrichment
  13. 2026-08-13 23:03 UTCMITRE cvelistV5CVSS v3 → 7.8 · severity → HIGH
  14. 2026-08-13 22:00 UTCEPSS rescore
  15. 2026-08-13 08:52 UTCEG score recompute
  16. 2026-08-13 08:52 UTCGHSA enrichment
  17. 2026-08-12 13:51 UTCEPSS rescore
  18. 2026-08-10 13:24 UTCNVD update
  19. 2026-08-10 12:17 UTCEG score recompute
  20. 2026-08-10 12:17 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-68419?
CVE-2026-68419 is a high vulnerability published on August 10, 2026. In the Linux kernel, the following vulnerability has been resolved: RDMA/irdma: Prevent rereg_mr for non-mem regions When a QP/CQ/SRQ is created, a two step process is used where the buffer is allocated in userspace and explicitly registered with the normal reg_mr mechanism prior to creating the…
When was CVE-2026-68419 disclosed?
CVE-2026-68419 was first published in the National Vulnerability Database on August 10, 2026, with the most recent update on August 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-68419 actively exploited?
CVE-2026-68419 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.1% of all scored CVEs.
What is the CVSS score of CVE-2026-68419?
CVE-2026-68419 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-68419?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-68419, 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-68419

Explore →

Is Your Infrastructure Affected by CVE-2026-68419?

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

Start Free Scan →Browse All CVEs