CVE-2026-74390

HIGHPre-NVD 7.87.8
EchelonGraph scoreHIGH confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 5 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: Fix out-of-bounds write in irdma_copy_user_pgaddrs

The irdma_copy_user_pgaddrs function loops through all of the umem DMA blocks to populate the PBLEs and will stop when either the last DMA block is reached or palloc->total_cnt is reached. The issue is that the logic for checking palloc->total_cnt would only work for non-zero values.

When irdma_setup_pbles is called with lvl==0, it calls irdma_copy_user_pgaddrs with palloc->total_cnt==0, which means the only way to break out of the loop is to reach the last umem DMA block, which means it could end up going beyond the fixed size of 4 iwmr->pgaddrmem array that is used in the lvl==0 case.

In the case of QP/CQ/SRQ rings, the value of lvl is determined by a separate input (for example, req.cq_pages in the case of a CQ). So, we must perform explicit checking to ensure we don't overflow the pgaddrmem array if the user provides a umem that consists of more blocks than their provided req.cq_pages.

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 15, 2026

Last Modified

August 17, 2026

Advisory Details (7)

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

RDMA/irdma: Fix out-of-bounds write in irdma_copy_user_pgaddrs - kernel/git/stable/linux.git - Linux kernel stable tree

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

RDMA/irdma: Fix out-of-bounds write in irdma_copy_user_pgaddrs - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/9f8f0d2099e3de1194e37dc933ae0c4206b09aaf
generic

RDMA/irdma: Fix out-of-bounds write in irdma_copy_user_pgaddrs - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/79a20a8e201a779224b4bf115250a7713bde72c0
generic

RDMA/irdma: Fix out-of-bounds write in irdma_copy_user_pgaddrs - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/5ebb3ed757be3e04cf803026004aa0beaeb13e9b
generic

RDMA/irdma: Fix out-of-bounds write in irdma_copy_user_pgaddrs - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/4780f58672ee6328accd54a95f9c00683477e499
generic

RDMA/irdma: Fix out-of-bounds write in irdma_copy_user_pgaddrs - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/424d51d33c7541a86934067c2c0538124687fc90
generic

RDMA/irdma: Fix out-of-bounds write in irdma_copy_user_pgaddrs - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/192a3be0e3759daa24af2841208b074ca6dbaabc

Vendor Advisories for CVE-2026-74390(1)

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 29× in last 7d / 29× 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 20:38 UTCGHSA enrichment
  3. 2026-08-20 08:21 UTCGHSA enrichment
  4. 2026-08-19 20:05 UTCEG score recompute
  5. 2026-08-19 20:05 UTCGHSA enrichment
  6. 2026-08-19 17:04 UTCEPSS rescore
  7. 2026-08-19 07:49 UTCGHSA enrichment
  8. 2026-08-18 19:30 UTCEG score recompute
  9. 2026-08-18 19:30 UTCGHSA enrichment
  10. 2026-08-18 13:49 UTCEPSS rescore
  11. 2026-08-18 13:49 UTCEPSS rescore
  12. 2026-08-18 07:13 UTCGHSA enrichment
  13. 2026-08-17 18:56 UTCEG score recompute
  14. 2026-08-17 18:56 UTCGHSA enrichment
  15. 2026-08-17 13:47 UTCEPSS rescore
  16. 2026-08-17 06:26 UTCEG score recompute
  17. 2026-08-17 06:26 UTCGHSA enrichment
  18. 2026-08-17 05:56 UTCEG score recompute 7.80
  19. 2026-08-17 05:56 UTCGHSA enrichment
  20. 2026-08-17 05:54 UTCMITRE cvelistV5CVSS v3 → 7.8 · severity → HIGH
  21. 2026-08-17 05:26 UTCEG score recompute
  22. 2026-08-17 05:26 UTCGHSA enrichment
  23. 2026-08-17 05:25 UTCMITRE cvelistV5
  24. 2026-08-16 14:56 UTCEPSS rescore
  25. 2026-08-16 14:56 UTCEPSS rescore
Show 4 more
  1. 2026-08-16 02:15 UTCEPSS rescore
  2. 2026-08-15 06:23 UTCNVD update
  3. 2026-08-15 06:14 UTCEG score recompute
  4. 2026-08-15 06:12 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-74390?
CVE-2026-74390 is a high vulnerability published on August 15, 2026. In the Linux kernel, the following vulnerability has been resolved: RDMA/irdma: Fix out-of-bounds write in irdmacopyuser_pgaddrs The irdmacopyuser_pgaddrs function loops through all of the umem DMA blocks to populate the PBLEs and will stop when either the last DMA block is reached or…
When was CVE-2026-74390 disclosed?
CVE-2026-74390 was first published in the National Vulnerability Database on August 15, 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-74390 actively exploited?
CVE-2026-74390 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.0% of all scored CVEs.
What is the CVSS score of CVE-2026-74390?
CVE-2026-74390 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-74390?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-74390, 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-74390

Explore →

Is Your Infrastructure Affected by CVE-2026-74390?

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