CVE-2026-46325

CRITICALPre-NVD 9.89.8
EchelonGraph scoreMEDIUM confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: cna:linux, epss, ghsa
Trending — 4 sources updated this week
9.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: 9.8Exploit: None knownExposed: 0

A fix is available — apply it.

In the Linux kernel, the following vulnerability has been resolved:

RDMA/rxe: Fix iova-to-va conversion for MR page sizes != PAGE_SIZE

The current implementation incorrectly handles memory regions (MRs) with page sizes different from the system PAGE_SIZE. The core issue is that rxe_set_page() is called with mr->page_size step increments, but the page_list stores individual struct page pointers, each representing PAGE_SIZE of memory.

ib_sg_to_page() has ensured that when i>=1 either a) SG[i-1].dma_end and SG[i].dma_addr are contiguous or b) SG[i-1].dma_end and SG[i].dma_addr are mr->page_size aligned.

This leads to incorrect iova-to-va conversion in scenarios:

1) page_size < PAGE_SIZE (e.g., MR: 4K, system: 64K): ibmr->iova = 0x181800 sg[0]: dma_addr=0x181800, len=0x800 sg[1]: dma_addr=0x173000, len=0x1000

Access iova = 0x181800 + 0x810 = 0x182010 Expected VA: 0x173010 (second SG, offset 0x10) Before fix:

  • index = (0x182010 >> 12) - (0x181800 >> 12) = 1
  • page_offset = 0x182010 & 0xFFF = 0x10
  • xarray[1] stores system page base 0x170000
  • Resulting VA: 0x170000 + 0x10 = 0x170010 (wrong)

2) page_size > PAGE_SIZE (e.g., MR: 64K, system: 4K): ibmr->iova = 0x18f800 sg[0]: dma_addr=0x18f800, len=0x800 sg[1]: dma_addr=0x170000, len=0x1000

Access iova = 0x18f800 + 0x810 = 0x190010 Expected VA: 0x170010 (second SG, offset 0x10) Before fix:

  • index = (0x190010 >> 16) - (0x18f800 >> 16) = 1
  • page_offset = 0x190010 & 0xFFFF = 0x10
  • xarray[1] stores system page for dma_addr 0x170000
  • Resulting VA: system page of 0x170000 + 0x10 = 0x170010 (wrong)

Yi Zhang reported a kernel panic[1] years ago related to this defect.

Solution:

  • Replace xarray with pre-allocated rxe_mr_page array for sequential
indexing (all MR page indices are contiguous)
  • Each rxe_mr_page stores both struct page* and offset within the
system page
  • Handle MR page_size != PAGE_SIZE relationships:
  • page_size > PAGE_SIZE: Split MR pages into multiple system pages
  • page_size <= PAGE_SIZE: Store offset within system page
  • Add boundary checks and compatibility validation

This ensures correct iova-to-va conversion regardless of MR page size and system PAGE_SIZE relationship, while improving performance through array-based sequential access.

Tests on 4K and 64K PAGE_SIZE hosts:

  • rdma-core/pytests
$ ./build/bin/run_tests.py --dev eth0_rxe
  • blktest:
$ TIMEOUT=30 QUICK_RUN=1 USE_RXE=1 NVMET_TRTYPES=rdma ./check nvme srp rnbd

[1] https://lore.kernel.org/all/CAHj4cs9XRqE25jyVw9rj9YugffLn5+f=1znaBEnu1usLOciD+g@mail.gmail.com/T/

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

Published

June 9, 2026

Last Modified

August 5, 2026

Advisory Details (3)

Auto-updated Sep 9, 2026
No patch confirmed yet.
generic

RDMA/rxe: Fix iova-to-va conversion for MR page sizes != PAGE_SIZE - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/12985e5915a0b8354796efadaaeb201eed115377
generic

RDMA/rxe: Fix iova-to-va conversion for MR page sizes != PAGE_SIZE - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/836f6c13c9674027793f720be3f15ecd2b90b6ca
generic

RDMA/rxe: Fix iova-to-va conversion for MR page sizes != PAGE_SIZE - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/409c2c5508f3d30627bea576f8676de523cb906e

Vendor Advisories for CVE-2026-46325(2)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(14)

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(2 across 2 ecosystems)
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.2~rc7-1~exp1 (174 versions)
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 6.18~rc7-1~exp1 (103 versions)6.18.14-1

All Vendor Advisories

(14)

Data Freshness Timeline

(refreshed 11× in last 7d / 67× 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 522 total refreshes for this CVE.

  1. 2026-09-16 05:15 UTCEPSS rescore
  2. 2026-09-14 08:42 UTCVendor advisory
  3. 2026-09-14 08:41 UTCGHSA enrichment
  4. 2026-09-14 04:39 UTCEG score recompute
  5. 2026-09-14 04:39 UTCVendor advisory
  6. 2026-09-14 04:38 UTCGHSA enrichment
  7. 2026-09-13 16:47 UTCEPSS rescore
  8. 2026-09-12 15:01 UTCEPSS rescore
  9. 2026-09-11 14:53 UTCEPSS rescore
  10. 2026-09-11 09:37 UTCEPSS rescore
  11. 2026-09-10 09:34 UTCEPSS rescore
  12. 2026-09-08 22:00 UTCEPSS rescore
  13. 2026-09-07 16:01 UTCEPSS rescore
  14. 2026-09-06 13:47 UTCEPSS rescore
  15. 2026-09-04 05:06 UTCEPSS rescore
  16. 2026-09-02 14:12 UTCEPSS rescore
  17. 2026-09-01 13:54 UTCEPSS rescore
  18. 2026-08-31 00:57 UTCEG score recompute
  19. 2026-08-31 00:57 UTCVendor advisory
  20. 2026-08-31 00:56 UTCGHSA enrichment
  21. 2026-08-30 19:17 UTCEPSS rescore
  22. 2026-08-30 01:22 UTCEPSS rescore
  23. 2026-08-28 21:41 UTCEPSS rescore
  24. 2026-08-27 14:25 UTCEPSS rescore
  25. 2026-08-26 14:46 UTCEPSS rescore
Show 75 more
  1. 2026-08-25 13:49 UTCEPSS rescore
  2. 2026-08-25 04:54 UTCVendor advisory
  3. 2026-08-25 04:54 UTCGHSA enrichment
  4. 2026-08-25 00:52 UTCEG score recompute
  5. 2026-08-25 00:52 UTCVendor advisory
  6. 2026-08-25 00:52 UTCGHSA enrichment
  7. 2026-08-23 23:42 UTCVendor advisory
  8. 2026-08-23 23:41 UTCGHSA enrichment
  9. 2026-08-23 19:24 UTCVendor advisory
  10. 2026-08-23 19:24 UTCGHSA enrichment
  11. 2026-08-23 15:21 UTCVendor advisory
  12. 2026-08-23 15:20 UTCGHSA enrichment
  13. 2026-08-23 11:18 UTCEG score recompute
  14. 2026-08-23 11:18 UTCVendor advisory
  15. 2026-08-23 11:17 UTCGHSA enrichment
  16. 2026-08-23 00:19 UTCEPSS rescore
  17. 2026-08-21 23:52 UTCEG score recompute
  18. 2026-08-21 23:52 UTCVendor advisory
  19. 2026-08-21 23:52 UTCGHSA enrichment
  20. 2026-08-21 23:49 UTCEPSS rescore
  21. 2026-08-21 19:47 UTCVendor advisory
  22. 2026-08-21 19:47 UTCGHSA enrichment
  23. 2026-08-21 12:24 UTCVendor advisory
  24. 2026-08-21 12:24 UTCGHSA enrichment
  25. 2026-08-21 06:40 UTCVendor advisory
  26. 2026-08-21 06:40 UTCGHSA enrichment
  27. 2026-08-21 01:32 UTCEG score recompute
  28. 2026-08-21 01:32 UTCVendor advisory
  29. 2026-08-21 01:31 UTCGHSA enrichment
  30. 2026-08-20 22:55 UTCEPSS rescore
  31. 2026-08-20 21:29 UTCVendor advisory
  32. 2026-08-20 21:29 UTCGHSA enrichment
  33. 2026-08-20 17:26 UTCVendor advisory
  34. 2026-08-20 17:26 UTCGHSA enrichment
  35. 2026-08-20 09:20 UTCEG score recompute
  36. 2026-08-20 09:20 UTCVendor advisory
  37. 2026-08-20 09:20 UTCGHSA enrichment
  38. 2026-08-19 17:04 UTCEPSS rescore
  39. 2026-08-18 13:48 UTCEPSS rescore
  40. 2026-08-17 13:47 UTCEPSS rescore
  41. 2026-08-17 12:58 UTCVendor advisory
  42. 2026-08-17 12:58 UTCGHSA enrichment
  43. 2026-08-17 08:56 UTCVendor advisory
  44. 2026-08-17 08:56 UTCGHSA enrichment
  45. 2026-08-17 04:54 UTCVendor advisory
  46. 2026-08-17 04:54 UTCGHSA enrichment
  47. 2026-08-17 00:52 UTCVendor advisory
  48. 2026-08-17 00:52 UTCGHSA enrichment
  49. 2026-08-16 16:49 UTCEG score recompute
  50. 2026-08-16 16:49 UTCVendor advisory
  51. 2026-08-16 16:49 UTCGHSA enrichment
  52. 2026-08-16 14:56 UTCEPSS rescore
  53. 2026-08-16 12:47 UTCVendor advisory
  54. 2026-08-16 12:47 UTCGHSA enrichment
  55. 2026-08-16 08:44 UTCVendor advisory
  56. 2026-08-16 08:44 UTCGHSA enrichment
  57. 2026-08-16 04:42 UTCEG score recompute
  58. 2026-08-16 04:42 UTCVendor advisory
  59. 2026-08-16 04:42 UTCGHSA enrichment
  60. 2026-08-16 02:14 UTCEPSS rescore
  61. 2026-08-16 00:40 UTCVendor advisory
  62. 2026-08-16 00:40 UTCGHSA enrichment
  63. 2026-08-15 19:46 UTCVendor advisory
  64. 2026-08-15 19:46 UTCGHSA enrichment
  65. 2026-08-15 15:37 UTCVendor advisory
  66. 2026-08-15 15:37 UTCGHSA enrichment
  67. 2026-08-15 11:35 UTCVendor advisory
  68. 2026-08-15 11:35 UTCGHSA enrichment
  69. 2026-08-15 02:39 UTCEG score recompute
  70. 2026-08-15 02:39 UTCVendor advisory
  71. 2026-08-15 02:39 UTCGHSA enrichment
  72. 2026-08-15 01:30 UTCEPSS rescore
  73. 2026-08-14 22:35 UTCVendor advisory
  74. 2026-08-14 22:35 UTCGHSA enrichment
  75. 2026-08-14 18:33 UTCVendor advisory

Frequently asked(5)

What is CVE-2026-46325?
CVE-2026-46325 is a critical vulnerability published on June 9, 2026. In the Linux kernel, the following vulnerability has been resolved: RDMA/rxe: Fix iova-to-va conversion for MR page sizes != PAGE_SIZE The current implementation incorrectly handles memory regions (MRs) with page sizes different from the system PAGE_SIZE. The core issue is that rxesetpage() is…
When was CVE-2026-46325 disclosed?
CVE-2026-46325 was first published in the National Vulnerability Database on June 9, 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-46325 actively exploited?
CVE-2026-46325 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 72.0% of all scored CVEs.
What is the CVSS score of CVE-2026-46325?
CVE-2026-46325 has a CVSS v4.0 base score of 9.8 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-46325?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-46325, 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-46325

Explore →

Is Your Infrastructure Affected by CVE-2026-46325?

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