CVE-2026-46325

CRITICALPre-NVD 9.89.8
EchelonGraph scoreHIGH confidence

Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2026-06-09. a secondary CVSS source baseline 9.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
9.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 9.8Exploit: NoneExposed: 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(high)
EPSS
26.7%
KEV
Not listed

Published

June 9, 2026

Last Modified

June 14, 2026

Advisory Details (3)

Auto-updated Jun 21, 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/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
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

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(2)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-virtual-hwe-24.04-edge (6.17.0-40.40) @ questing2026-07-06ubuntu
ubuntulinux-tools-oem-6.17 (6.17.0-1028.28) @ noble2026-07-06ubuntu

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.

All Vendor Advisories

(2)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

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

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

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 June 14, 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 26.7% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-46325?
CVE-2026-46325 has a CVSS v3 base score of 9.8 (NVD).
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

Explore the affected products and dependency analysis for 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.