CVE-2026-52908

HIGHPre-NVD 7.87.8—
EchelonGraph scoreMEDIUM confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-06-19. the CNA's CVSS baseline 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cna:linux, epss, ghsa
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: 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(medium)
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

June 19, 2026

Last Modified

August 5, 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.

Affected Packages

(2 across 2 ecosystems)
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.94-1~bpo12+1 (27 versions)6.12.94-1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.0.9-1~bpo13+1 (145 versions)7.0.13-1—

Data Freshness Timeline

(refreshed 5× in last 7d / 77× 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.

Showing the most recent 100 of 267 total refreshes for this CVE.

  1. 2026-09-11 14:53 UTCEPSS rescore
  2. 2026-09-10 09:35 UTCEPSS rescore
  3. 2026-09-08 22:01 UTCEPSS rescore
  4. 2026-09-07 16:01 UTCEPSS rescore
  5. 2026-09-06 13:47 UTCEPSS rescore
  6. 2026-09-04 05:06 UTCEPSS rescore
  7. 2026-09-02 14:12 UTCEPSS rescore
  8. 2026-09-01 13:54 UTCEPSS rescore
  9. 2026-09-01 04:40 UTCEPSS rescore
  10. 2026-08-30 20:50 UTCEG score recompute
  11. 2026-08-30 20:50 UTCVendor advisory
  12. 2026-08-30 20:50 UTCGHSA enrichment
  13. 2026-08-30 19:17 UTCEPSS rescore
  14. 2026-08-30 01:22 UTCEPSS rescore
  15. 2026-08-28 21:41 UTCEPSS rescore
  16. 2026-08-27 14:25 UTCEPSS rescore
  17. 2026-08-26 14:46 UTCEPSS rescore
  18. 2026-08-25 13:49 UTCEPSS rescore
  19. 2026-08-25 02:37 UTCVendor advisory
  20. 2026-08-25 02:37 UTCGHSA enrichment
  21. 2026-08-24 14:33 UTCEG score recompute
  22. 2026-08-24 14:33 UTCVendor advisory
  23. 2026-08-24 14:32 UTCGHSA enrichment
  24. 2026-08-23 23:55 UTCVendor advisory
  25. 2026-08-23 23:54 UTCGHSA enrichment
Show 75 more
  1. 2026-08-23 11:53 UTCEG score recompute
  2. 2026-08-23 11:53 UTCVendor advisory
  3. 2026-08-23 11:53 UTCGHSA enrichment
  4. 2026-08-23 00:19 UTCEPSS rescore
  5. 2026-08-22 23:52 UTCEG score recompute
  6. 2026-08-22 23:52 UTCVendor advisory
  7. 2026-08-22 23:52 UTCGHSA enrichment
  8. 2026-08-21 23:49 UTCEPSS rescore
  9. 2026-08-21 20:10 UTCGHSA enrichment
  10. 2026-08-21 08:09 UTCEG score recompute
  11. 2026-08-21 08:09 UTCVendor advisory
  12. 2026-08-21 08:09 UTCGHSA enrichment
  13. 2026-08-20 22:55 UTCEPSS rescore
  14. 2026-08-20 20:07 UTCVendor advisory
  15. 2026-08-20 20:07 UTCGHSA enrichment
  16. 2026-08-20 08:06 UTCEG score recompute
  17. 2026-08-20 08:06 UTCVendor advisory
  18. 2026-08-20 08:06 UTCGHSA enrichment
  19. 2026-08-19 17:04 UTCEPSS rescore
  20. 2026-08-19 07:18 UTCEG score recompute
  21. 2026-08-19 07:18 UTCVendor advisory
  22. 2026-08-19 07:18 UTCGHSA enrichment
  23. 2026-08-18 13:48 UTCEPSS rescore
  24. 2026-08-17 14:54 UTCEG score recompute
  25. 2026-08-17 14:54 UTCVendor advisory
  26. 2026-08-17 14:54 UTCGHSA enrichment
  27. 2026-08-17 13:47 UTCEPSS rescore
  28. 2026-08-17 02:53 UTCEG score recompute
  29. 2026-08-17 02:53 UTCVendor advisory
  30. 2026-08-17 02:53 UTCGHSA enrichment
  31. 2026-08-16 14:56 UTCEPSS rescore
  32. 2026-08-16 14:51 UTCVendor advisory
  33. 2026-08-16 14:51 UTCGHSA enrichment
  34. 2026-08-16 02:49 UTCEG score recompute
  35. 2026-08-16 02:49 UTCVendor advisory
  36. 2026-08-16 02:49 UTCGHSA enrichment
  37. 2026-08-16 02:14 UTCEPSS rescore
  38. 2026-08-15 14:48 UTCVendor advisory
  39. 2026-08-15 14:48 UTCGHSA enrichment
  40. 2026-08-15 02:46 UTCEG score recompute
  41. 2026-08-15 02:46 UTCVendor advisory
  42. 2026-08-15 02:46 UTCGHSA enrichment
  43. 2026-08-15 01:30 UTCEPSS rescore
  44. 2026-08-14 14:40 UTCVendor advisory
  45. 2026-08-14 14:40 UTCGHSA enrichment
  46. 2026-08-14 02:39 UTCEG score recompute
  47. 2026-08-14 02:39 UTCVendor advisory
  48. 2026-08-14 02:39 UTCGHSA enrichment
  49. 2026-08-13 22:00 UTCEPSS rescore
  50. 2026-08-13 14:37 UTCVendor advisory
  51. 2026-08-13 14:37 UTCGHSA enrichment
  52. 2026-08-13 02:21 UTCGHSA enrichment
  53. 2026-08-12 14:20 UTCEG score recompute
  54. 2026-08-12 14:20 UTCVendor advisory
  55. 2026-08-12 14:20 UTCGHSA enrichment
  56. 2026-08-12 13:51 UTCEPSS rescore
  57. 2026-08-12 02:17 UTCVendor advisory
  58. 2026-08-12 02:17 UTCGHSA enrichment
  59. 2026-08-11 14:15 UTCEG score recompute
  60. 2026-08-11 14:15 UTCVendor advisory
  61. 2026-08-11 14:15 UTCGHSA enrichment
  62. 2026-08-11 02:13 UTCEG score recompute
  63. 2026-08-11 02:13 UTCVendor advisory
  64. 2026-08-11 02:13 UTCGHSA enrichment
  65. 2026-08-11 00:00 UTCEPSS rescore
  66. 2026-08-10 14:12 UTCVendor advisory
  67. 2026-08-10 14:12 UTCGHSA enrichment
  68. 2026-08-10 02:11 UTCVendor advisory
  69. 2026-08-10 02:11 UTCGHSA enrichment
  70. 2026-08-09 14:09 UTCEG score recompute
  71. 2026-08-09 14:09 UTCVendor advisory
  72. 2026-08-09 14:09 UTCGHSA enrichment
  73. 2026-08-09 13:46 UTCEPSS rescore
  74. 2026-08-09 02:08 UTCVendor advisory
  75. 2026-08-09 02:08 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 August 5, 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 0% probability of exploitation in the next 30 days, which ranks it in the top 97.2% of all scored CVEs.
What is the CVSS score of CVE-2026-52908?
CVE-2026-52908 has a CVSS v4.0 base score of 7.8 (CNA self-assessment; NVD's own analysis pending).
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

See which npm, PyPI, Go, and Maven packages are affected by 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