Skip to main content

Linux Kernel EUVDEUVD-2026-35426

| CVE-2026-46325 CRITICAL
Integer Overflow or Wraparound (CWE-190)
2026-06-09 Linux GHSA-rmw9-5h46-94mm
Critical
Disputed · 9.8 Vendor: Linux
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Gain RDMA verbs access (local user or fabric peer)
  2. Delivery
    Load/use rxe Soft-RoCE module
  3. Exploit
    Register MR with mismatched page_size
  4. Execution
    Issue RDMA op crossing SG boundary
  5. Persist
    Trigger wrong iova-to-VA translation
  6. Impact
    Kernel panic or out-of-bounds memory access

Vulnerability Assessment

Weakness
CWE
ASVS 5.0
V15 - Secure Coding and Architecture Integer overflow checks
MITRE ATT&CK

1 technique across 1 tactic: Execution

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

Exploitation requires the rxe (Soft-RoCE) kernel module to be loaded and an attacker capable of issuing RDMA verbs against it - typically a local process with access to /dev/infiniband/uverbs* (group rdma) or a remote RDMA peer already attached to the same Soft-RoCE fabric. The attacker must register a Memory Region whose mr->page_size does not equal the host's system PAGE_SIZE (commonly 4K MR on a 64K-page arm64/ppc64le kernel, or 64K MR on a 4K-page x86_64 kernel) and then perform an RDMA operation whose iova straddles the affected scatter-gather boundary. Limiting factors that materially reduce real-world risk: rxe is not loaded by default on most server distributions; hosts using hardware RDMA NICs (mlx5, etc.) typically do not enable rxe; the CVSS AV:N rating overstates reachability because the attacker must already be on the RDMA fabric or local to the box; and only kernels 6.3 through pre-6.18.14/6.19.4/7.0 are affected.

Impact

Signals here conflict sharply and deserve careful weighting. NVD records CVSS 9.8 (AV:N/AC:L/PR:N/UI:N/C:H/I:H/A:H), implying remote unauthenticated full compromise, yet the actual code path requires a process to have established an RDMA Memory Region via rxe and issued RDMA operations with a mismatched page size - this is fundamentally a local/RDMA-fabric condition, not raw internet reachability, so the AV:N rating is almost certainly inflated. EPSS is only 0.02% (4th percentile), the bug is not on CISA KEV, and no public exploit identified at time of analysis. The realistic outcome demonstrated in the report is a kernel panic (DoS) and erroneous memory reads/writes for RDMA peers; reliable, weaponized RCE from an unauthenticated remote source is not established by available data. Real-world priority is moderate: patch promptly on hosts that load the rxe module (NVMe-oF/RDMA targets, SDS clusters, HPC nodes), but it does not warrant emergency 9.8-level response on systems where rxe is not loaded.

Exploit ScenarioDerived

A local user with permission to use RDMA verbs (or a remote peer already authorized on the RDMA fabric) registers a Memory Region whose page size differs from the host's system PAGE_SIZE - e.g., a 4K-MR on a 64K-page kernel - then issues an RDMA read/write that triggers the miscomputed iova-to-VA translation. The kernel dereferences a struct page from an adjacent SG entry, causing either a kernel panic (denial of service, as Yi Zhang's report demonstrated) or read/write into unrelated kernel-mapped memory, potentially yielding information disclosure or memory corruption. No public exploit identified at time of analysis.

Act Now Prioritize within 24-48h. Why: CRITICAL severity.
Patch available 0.0% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Jun 14, 2026

Memory corruption in the Linux kernel's RDMA Soft-RoCE (rxe) driver allows incorrect iova-to-virtual-address translation when Memory Region (MR) page sizes differ from the system PAGE_SIZE, leading to access of wrong memory pages during RDMA operations. The flaw affects kernels from 6.3 through pre-6.18.14 / pre-6.19.4 / pre-7.0 patched releases, and a related kernel panic was previously reported by Yi Zhang. EPSS is 0.02% (4th percentile) and no public exploit identified at time of analysis, but a patch is available from upstream.

RemediationAI

Vendor-released patch: upgrade to Linux 6.18.14, 6.19.4, or 7.0 (with the fix) or later, pulling the upstream commits 409c2c5508f3d30627bea576f8676de523cb906e, 836f6c13c9674027793f720be3f15ecd2b90b6ca, and 12985e5915a0b8354796efadaaeb201eed115377 from git.kernel.org/stable; distribution users should monitor their vendor advisory channel and apply the backported kernel update. If patching must be deferred, the most effective compensating control is to avoid loading the rxe module (blacklist rdma_rxe via /etc/modprobe.d/) on hosts that do not require Soft-RoCE - trade-off: this disables software RDMA emulation, which is acceptable when hardware RNICs or non-RDMA transports are in use but breaks NVMe-oF/RDMA, SRP, and similar workloads running on top of rxe. Where rxe must remain enabled, restrict which userspace processes can open /dev/infiniband/uverbs* (typically via group rdma membership) to reduce who can register MRs with non-default page sizes, and ensure RDMA fabric peers are trusted, since the bug is reachable by RDMA traffic from peers that have established a connection. See https://nvd.nist.gov/vuln/detail/CVE-2026-46325 for tracking.

Affected VersionsENISA

Linux patch: 6.18.14
Linux 0e443760b8b7b1e6723f4408afa056b2bc4fea12
Linux 592627ccbdff0ec6fff00fc761142a76db750dd4 <409c2c5508f3d30627bea576f8676de523cb906e
Linux 6.2.3 <6.3
Linux 6.3
Linux patch: 0
Linux patch: 6.19.4
Linux 592627ccbdff0ec6fff00fc761142a76db750dd4 <836f6c13c9674027793f720be3f15ecd2b90b6ca
Linux 592627ccbdff0ec6fff00fc761142a76db750dd4 <12985e5915a0b8354796efadaaeb201eed115377
Linux patch: 7.0

Affected Packages

euvd linux fix: 6.3

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

The vulnerability sits in drivers/infiniband/sw/rxe (Soft-RoCE), the software RDMA-over-Converged-Ethernet implementation that emulates InfiniBand verbs over standard Ethernet. The rxe_set_page() routine populated an xarray of struct page pointers using mr->page_size step increments, but each xarray slot represents one system PAGE_SIZE-sized page. When MR page_size and system PAGE_SIZE diverge (e.g., 4K MR on a 64K kernel, or 64K MR on a 4K kernel), the index/offset math used for iova-to-VA conversion dereferences the wrong scatter-gather entry, returning a virtual address that points into unrelated memory. The fix replaces the xarray with a pre-allocated rxe_mr_page array that stores both struct page* and the offset within the system page, plus boundary and compatibility checks. No CWE was assigned, but functionally this is an out-of-bounds / incorrect-pointer-arithmetic class defect in kernel memory mapping logic.

Know when the next one hits your stack

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Sources disagree (Medium–Critical)
Vendor (Linux) PRIMARY 9.8 CRITICAL
AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
vuln.today AI 5.8 MEDIUM

Requires local RDMA verbs access (PR:L, AV:L), a non-default MR/PAGE_SIZE mismatch and SG-boundary timing (AC:H); primary demonstrated impact is kernel panic (A:H) with limited memory disclosure/corruption (C:L/I:L).

3.1 AV:L/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:H
4.0 AV:L/AC:H/AT:P/PR:L/UI:N/VC:L/VI:L/VA:H/SC:N/SI:N/SA:N
SUSE 5.7 MEDIUM
AV:A/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Red Hat 7.0 MEDIUM

vuln.today treats the vendor’s rating as authoritative. A higher third-party CVSS (e.g. CISA-ADP) is shown for transparency but does not drive the headline severity.

CVSS VectorVendor: Linux

Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

Lifecycle Timeline

4
CVSS changed
Jun 14, 2026 - 06:22 NVD
9.8 (CRITICAL)
Patch available
Jun 09, 2026 - 15:01 EUVD
CVE Published
Jun 09, 2026 - 12:25 cve.org
CRITICAL 9.8
CVE Published
Jun 09, 2026 - 12:25 nvd
UNKNOWN (no severity yet)

DescriptionCVE.org

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)
  1. 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)

  1. Each rxe_mr_page stores both struct page* and offset within the

system page

  1. 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
  1. 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/

Executive ViewAI

Why It Matters

A critical memory corruption vulnerability in the Linux kernel's RDMA Soft-RoCE driver (CVE-2026-46325, CVSS 9.8) enables unauthorized memory access on systems processing RDMA operations. Organizations deploying Linux infrastructure with RDMA-enabled systems-particularly those using high-speed storage or networking-face risk of data breach and infrastructure compromise, though current exploitation likelihood remains minimal.

Business Impact: Severe
Compensating Controls

Apply vendor patch. As interim mitigation if patching is delayed, disable RDMA modules (modprobe -r ib_core) on non-critical systems; this eliminates attack surface but will degrade performance for RDMA-dependent workloads.

Threat Intelligence Overview

EPSS Score
0.0%
Top 96% exploitable
Data Quality
6 sources
Confidence: High

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity CRITICAL
CISA KEV No
Public POC No
EPSS 0.0%
Patch available Yes
Active threat No
Deciding rule
CRITICAL severity
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Out-of-Cycle
Exploitation· derived
None
System Exposure· derived
Open
Automatable· derived
Yes
Human Impact
Very High

Priority Score

49
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +49
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Integer overflow occurs when an arithmetic operation produces a result that exceeds the maximum value a given integer type can store.

Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.

Vendor StatusVendor

SUSE

Severity: Moderate
Product Status
SUSE Linux Enterprise Desktop 15 SP7 Affected
SUSE Linux Enterprise Desktop 15 SP7 Affected
SUSE Linux Enterprise High Availability Extension 15 SP7 Affected
SUSE Linux Enterprise High Availability Extension 15 SP7 Affected
SUSE Linux Enterprise High Performance Computing 15 SP7 Affected

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy