CVE-2026-52908

HIGHPre-NVD 7.87.8—
EchelonGraph scoreHIGH confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-06-19. 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.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.8Exploit: NoneExposed: 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: During rereg_mr ensure that REREG_ACCESS is compatible

If IB_MR_REREG_ACCESS changes from RO to RW then the umem has to be re-evaluated to ensure it is properly pinned as RW. Since the umem is hidden inside each driver's mr struct add a ib_umem_check_rereg() function that each driver has to call before processing IB_MR_REREG_ACCESS.

mlx4 has to retain its duplicate ib_access_writable check because it implements IB_MR_REREG_ACCESS | IB_MR_REREG_TRANS by changing both items in place sequentially while the MR is live, so it will continue to not support this combination.

CVSS v3
7.8
EG Score
7.8(high)
EPSS
2.9%
KEV
Not listed

Published

June 19, 2026

Last Modified

June 28, 2026

Advisory Details (5)

Auto-updated Jun 28, 2026
No patch confirmed yet.
generic

RDMA: During rereg_mr ensure that REREG_ACCESS is compatible - kernel/git/stable/linux.git - Linux kernel stable tree

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

RDMA: During rereg_mr ensure that REREG_ACCESS is compatible - kernel/git/stable/linux.git - Linux kernel stable tree

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

RDMA: During rereg_mr ensure that REREG_ACCESS is compatible - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/50334a05a950840b39a1ce3d2a173b4183db9b3e
generic

RDMA: During rereg_mr ensure that REREG_ACCESS is compatible - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/2904e985a2917b5dac65df82733065e78a65fc9d
generic

RDMA: During rereg_mr ensure that REREG_ACCESS is compatible - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/09dc18894148381d3bfc550083b1236043870dce

Vendor Advisories for CVE-2026-52908(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 31× in last 7d / 48× 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-07-06 21:38 UTCEG score recompute
  2. 2026-07-06 21:38 UTCGHSA enrichment
  3. 2026-07-06 09:36 UTCEG score recompute
  4. 2026-07-06 09:36 UTCGHSA enrichment
  5. 2026-07-06 02:23 UTCEPSS rescore
  6. 2026-07-06 02:23 UTCEPSS rescore
  7. 2026-07-05 20:27 UTCEG score recompute
  8. 2026-07-05 20:27 UTCGHSA enrichment
  9. 2026-07-05 08:26 UTCEG score recompute
  10. 2026-07-05 08:25 UTCGHSA enrichment
  11. 2026-07-05 02:30 UTCEPSS rescore
  12. 2026-07-04 20:23 UTCEG score recompute
  13. 2026-07-04 20:23 UTCGHSA enrichment
  14. 2026-07-04 08:21 UTCEG score recompute
  15. 2026-07-04 08:21 UTCGHSA enrichment
  16. 2026-07-04 06:31 UTCEPSS rescore
  17. 2026-07-03 20:17 UTCEG score recompute
  18. 2026-07-03 20:17 UTCGHSA enrichment
  19. 2026-07-03 08:16 UTCEG score recompute
  20. 2026-07-03 08:16 UTCGHSA enrichment
  21. 2026-07-02 20:13 UTCEG score recompute
  22. 2026-07-02 20:13 UTCGHSA enrichment
  23. 2026-07-02 08:11 UTCEG score recompute
  24. 2026-07-02 08:11 UTCGHSA enrichment
  25. 2026-07-01 20:07 UTCEG score recompute
Show 23 more
  1. 2026-07-01 20:07 UTCGHSA enrichment
  2. 2026-07-01 15:07 UTCEPSS rescore
  3. 2026-07-01 08:05 UTCEG score recompute
  4. 2026-07-01 08:05 UTCGHSA enrichment
  5. 2026-06-30 20:03 UTCEG score recompute▲ 7.80
  6. 2026-06-30 20:03 UTCGHSA enrichment
  7. 2026-06-29 14:06 UTCEPSS rescore
  8. 2026-06-29 14:06 UTCEPSS rescore
  9. 2026-06-28 14:07 UTCEPSS rescore
  10. 2026-06-28 07:52 UTCMITRE cvelistV5CVSS v3 → 7.8 · severity → HIGH
  11. 2026-06-28 04:56 UTCEPSS rescore
  12. 2026-06-28 04:56 UTCEPSS rescore
  13. 2026-06-28 01:02 UTCGHSA enrichment
  14. 2026-06-27 03:08 UTCEPSS rescore
  15. 2026-06-25 13:49 UTCEPSS rescore
  16. 2026-06-25 06:00 UTCEG score recompute
  17. 2026-06-25 06:00 UTCGHSA enrichment
  18. 2026-06-24 14:05 UTCEPSS rescore
  19. 2026-06-23 21:33 UTCEPSS rescore
  20. 2026-06-23 21:33 UTCEPSS rescore
  21. 2026-06-22 10:58 UTCGHSA enrichment
  22. 2026-06-19 15:57 UTCEG score recompute
  23. 2026-06-19 15:56 UTCGHSA enrichment

Frequently asked(5)

What is CVE-2026-52908?
CVE-2026-52908 is a high vulnerability published on June 19, 2026. In the Linux kernel, the following vulnerability has been resolved: RDMA: During reregmr ensure that REREGACCESS is compatible If IBMRREREG_ACCESS changes from RO to RW then the umem has to be re-evaluated to ensure it is properly pinned as RW. Since the umem is hidden inside each driver's mr…
When was CVE-2026-52908 disclosed?
CVE-2026-52908 was first published in the National Vulnerability Database on June 19, 2026, with the most recent update on June 28, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-52908 actively exploited?
CVE-2026-52908 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 2.9% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-52908?
CVE-2026-52908 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-52908?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-52908, 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-52908

Explore →

Is Your Infrastructure Affected by CVE-2026-52908?

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

Start Free Scan →Browse All CVEs