CVE-2026-46325: RDMA/rxe: Fix iova-to-va conversion for MR page sizes != PAGE_SIZE
Noroxi assessment
Priority: Monitor (action score 39/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.45% (FIRST EPSS).
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- According to CISA the attack is automatable: targets can be found by mass scanning.
- Fixed version: Linux Linux 12985e5915a0b8354796efadaaeb201eed115377, 2a585a08a43c568ed6e9f27a97fd3d95106b9e68, 409c2c5508f3d30627bea576f8676de523cb906e; azl3 kernel 6.6.152.1-1 on Azure Linux 3.0 Release Notes; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 Release Notes.
Low priority for now. Upgrade to Linux Linux 12985e5915a0b8354796efadaaeb201eed115377, 2a585a08a43c568ed6e9f27a97fd3d95106b9e68, 409c2c5508f3d30627bea576f8676de523cb906e; azl3 kernel 6.6.152.1-1 on Azure Linux 3.0 Release Notes; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 Release Notes or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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: 1. Replace xarray with pre-allocated rxe_mr_page array for sequential indexing (all MR page indices are contiguous) 2. Each rxe_mr_page stores both struct page* and offset within the system page 3. 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 4. 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/
- Published
- Jun 9, 2026
- Updated
- Oct 21, 2026
- EPSS
- 0.4% · 39th percentile
- CWE
- CWE-190
Report tools
Action score
39
Monitor
Low priority for now.
- CVSS
- 39 / 40 · 9.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.4%
CISA SSVC decision
- Exploitation
- none
- Automatable
- yes
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · Linux
- 9.8
- NVD has not scored this yet; the score shown is the CNA’s.
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernel6.2.3 and later · before 6.18.14
- linux linux kernel6.19 and later · before 6.19.4
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 0e443760b8b7b1e6723f4408afa056b2bc4fea12, 6.3affected
- 592627ccbdff0ec6fff00fc761142a76db750dd4 and later · before e327021bd73b134c18167e2cd2a52eb5597fcba6affected · git
- 592627ccbdff0ec6fff00fc761142a76db750dd4 and later · before 2a585a08a43c568ed6e9f27a97fd3d95106b9e68affected · git
- 592627ccbdff0ec6fff00fc761142a76db750dd4 and later · before 409c2c5508f3d30627bea576f8676de523cb906eaffected · git
- 592627ccbdff0ec6fff00fc761142a76db750dd4 and later · before 836f6c13c9674027793f720be3f15ecd2b90b6caaffected · git
- 592627ccbdff0ec6fff00fc761142a76db750dd4 and later · before 12985e5915a0b8354796efadaaeb201eed115377affected · git
- 6.2.3 and later · before 6.3affected · semver
- before 6.3not affected · semver
- 6.6.160 and later · up to and including 6.6.*not affected · semver
- 6.12.114 and later · up to and including 6.12.*not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| AlmaLinux:9 | kernel | before 5.14.0-687.53.1.el9_8 | 5.14.0-687.53.1.el9_8 |
| AlmaLinux:9 | kernel-64k | before 5.14.0-687.53.1.el9_8 | 5.14.0-687.53.1.el9_8 |
| AlmaLinux:9 | kernel-64k-core | before 5.14.0-687.53.1.el9_8 | 5.14.0-687.53.1.el9_8 |
| AlmaLinux:9 | kernel-64k-debug | before 5.14.0-687.53.1.el9_8 | 5.14.0-687.53.1.el9_8 |
| AlmaLinux:9 | kernel-64k-debug-core | before 5.14.0-687.53.1.el9_8 | 5.14.0-687.53.1.el9_8 |
| AlmaLinux:9 | kernel-64k-debug-devel | before 5.14.0-687.53.1.el9_8 | 5.14.0-687.53.1.el9_8 |
| AlmaLinux:9 | kernel-64k-debug-devel-matched | before 5.14.0-687.53.1.el9_8 | 5.14.0-687.53.1.el9_8 |
| AlmaLinux:9 | kernel-64k-debug-modules | before 5.14.0-687.53.1.el9_8 | 5.14.0-687.53.1.el9_8 |
| AlmaLinux:9 | kernel-64k-debug-modules-core | before 5.14.0-687.53.1.el9_8 | 5.14.0-687.53.1.el9_8 |
| AlmaLinux:9 | kernel-64k-debug-modules-extra | before 5.14.0-687.53.1.el9_8 | 5.14.0-687.53.1.el9_8 |
| AlmaLinux:9 | kernel-64k-devel | before 5.14.0-687.53.1.el9_8 | 5.14.0-687.53.1.el9_8 |
| AlmaLinux:9 | kernel-64k-devel-matched | before 5.14.0-687.53.1.el9_8 | 5.14.0-687.53.1.el9_8 |
| AlmaLinux:9 | kernel-64k-modules | before 5.14.0-687.53.1.el9_8 | 5.14.0-687.53.1.el9_8 |
| AlmaLinux:9 | kernel-64k-modules-core | before 5.14.0-687.53.1.el9_8 | 5.14.0-687.53.1.el9_8 |
| AlmaLinux:9 | kernel-64k-modules-extra | before 5.14.0-687.53.1.el9_8 | 5.14.0-687.53.1.el9_8 |
| AlmaLinux:9 | kernel-abi-stablelists | before 5.14.0-687.53.1.el9_8 | 5.14.0-687.53.1.el9_8 |
| AlmaLinux:9 | kernel-core | before 5.14.0-687.53.1.el9_8 | 5.14.0-687.53.1.el9_8 |
| AlmaLinux:9 | kernel-cross-headers | before 5.14.0-687.53.1.el9_8 | 5.14.0-687.53.1.el9_8 |
| AlmaLinux:9 | kernel-debug | before 5.14.0-687.53.1.el9_8 | 5.14.0-687.53.1.el9_8 |
| AlmaLinux:9 | kernel-debug-core | before 5.14.0-687.53.1.el9_8 | 5.14.0-687.53.1.el9_8 |
| AlmaLinux:9 | kernel-debug-devel | before 5.14.0-687.53.1.el9_8 | 5.14.0-687.53.1.el9_8 |
| AlmaLinux:9 | kernel-debug-devel-matched | before 5.14.0-687.53.1.el9_8 | 5.14.0-687.53.1.el9_8 |
| AlmaLinux:9 | kernel-debug-modules | before 5.14.0-687.53.1.el9_8 | 5.14.0-687.53.1.el9_8 |
| AlmaLinux:9 | kernel-debug-modules-core | before 5.14.0-687.53.1.el9_8 | 5.14.0-687.53.1.el9_8 |
+96
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV90Now
- CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe…KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
Published before and after this one in the same product
- ← EarlierCVE-2026-46323Jun 9, 2026 · net: gro: don't merge zcopy skbs31Monitor
- ← EarlierCVE-2026-46324Jun 9, 2026 · netfilter: nf_tables: use list_del_rcu for netlink hooks31Monitor
- Later →CVE-2026-46327Jun 9, 2026 · dm: fix unlocked test for dm_suspended_md31Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 12985e5915a0b8354796efadaaeb201eed115377 | Vendor (CNA) |
| Linux Linux | 2a585a08a43c568ed6e9f27a97fd3d95106b9e68 | Vendor (CNA) |
| Linux Linux | 409c2c5508f3d30627bea576f8676de523cb906e | Vendor (CNA) |
| Linux Linux | 6.3 | Vendor (CNA) |
| Linux Linux | 836f6c13c9674027793f720be3f15ecd2b90b6ca | Vendor (CNA) |
| Linux Linux | e327021bd73b134c18167e2cd2a52eb5597fcba6 | Vendor (CNA) |
| azl3 kernel 6.6.152.1-1 on Azure Linux 3.0 | Release Notes | Microsoft (MSRC) |
| azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 | Release Notes | Microsoft (MSRC) |
| almalinux:kernel | 5.14.0-687.53.1.el9_8 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k | 5.14.0-687.53.1.el9_8 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-core | 5.14.0-687.53.1.el9_8 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-debug | 5.14.0-687.53.1.el9_8 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-debug-core | 5.14.0-687.53.1.el9_8 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-debug-devel | 5.14.0-687.53.1.el9_8 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-debug-devel-matched | 5.14.0-687.53.1.el9_8 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-debug-modules | 5.14.0-687.53.1.el9_8 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-debug-modules-core | 5.14.0-687.53.1.el9_8 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-debug-modules-extra | 5.14.0-687.53.1.el9_8 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-devel | 5.14.0-687.53.1.el9_8 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-devel-matched | 5.14.0-687.53.1.el9_8 · AlmaLinux:9 | Package registry (OSV) |
| debian:linux | 6.12.115-2 · Debian:13 | Package registry (OSV) |
| debian:linux | 6.18.14-1 · Debian:14 | Package registry (OSV) |
| red hat:kernel-64k-debug-debuginfo | 0:5.14.0-687.53.1.el9_8 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:kernel-64k-debug-devel | 0:5.14.0-687.53.1.el9_8 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:kernel-64k-debug-devel-matched | 0:5.14.0-687.53.1.el9_8 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:kernel-64k-debuginfo | 0:5.14.0-687.53.1.el9_8 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:kernel-64k-devel | 0:5.14.0-687.53.1.el9_8 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:kernel-64k-devel-matched | 0:5.14.0-687.53.1.el9_8 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:kernel-debug-debuginfo | 0:5.14.0-687.53.1.el9_8 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:kernel-debug-devel | 0:5.14.0-687.53.1.el9_8 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
+5
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2026-4603913 days apartrxgk: Fix potential integer overflow in length check39Monitor
- CVE-2026-4334132 days apartnet/ipv6: ioam6: prevent schema length wraparound in trace fill39Monitor
- CVE-2026-3163346 days apartrxrpc: Fix integer overflow in rxgk_verify_response()39Monitor
- CVE-2026-3164946 days apartnet: stmmac: fix integer underflow in chain mode39Monitor
- CVE-2026-3165946 days apartbatman-adv: reject oversized global TT response buffers39Monitor
- CVE-2026-4604313 days apartRDMA/rxe: Validate pad and ICRC before payload_size() in rxe_rcv36Monitor
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-190 · Integer Overflow or WraparoundCVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
—
Change log
- SSVC exploitation— → none
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (4 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.