Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessEstablish Soft-iWARP RDMA peer connection
-
DeliverySend DDP/RDMAP header split across TCP callbacks
-
ExploitOverflow receive state, force negative fpdu_part_rcvd
-
ExecutionTrigger out-of-bounds kernel write
-
ImpactCorrupt kernel memory / execute code
Vulnerability Assessment
| Exploitation Conditions | Exploitation requires the Linux Soft-iWARP driver (siw / rdma_rxe-style soft RDMA) to be loaded and an established iWARP RDMA connection in which the attacker is a connected peer - siw is not loaded in default Linux configurations, which is the primary limiting factor. The attacker must additionally control TCP segmentation so that an extended DDP/RDMAP header is delivered across more than one siw_get_hdr() receive callback, since the bug only manifests when the header spans multiple callbacks and the copy length is miscalculated to hdrlen - MIN_DDP_HDR. No OS-level authentication or user interaction is needed once an RDMA session exists, but the absence of siw on typical servers and the need to craft fragmented header delivery sharply narrow realistic exploitation. |
| Impact | The input CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N/C:H/I:H/A:H, base 9.8 CRITICAL) presents this as a remote, unauthenticated, trivially exploitable kernel memory-corruption bug. However, the quantitative threat signals strongly contradict that worst-case framing: EPSS is only 0.18% (7th percentile), there is no CISA KEV listing, and no public proof-of-concept is referenced - so this is 'no public exploit identified at time of analysis.' The low EPSS despite a 9.8 base score is best explained by the narrow attack surface: the flaw lives in the siw (Soft-iWARP) RDMA driver, which is not loaded by default and requires an established iWARP RDMA connection to reach. I disagree with AC:L in the supplied vector - reliably driving fpdu_part_rcvd negative requires the attacker to control TCP segmentation so the extended DDP/RDMAP header arrives split across multiple socket callbacks and to manipulate receive-buffer state, which is non-trivial; AC:H is more defensible (see assessed vector). Net: a genuine critical-severity kernel OOB write worth patching promptly on any host that actually uses Soft-iWARP, but a low real-world-urgency issue for the overwhelming majority of Linux systems that never load the siw module. Treat prioritization as config-dependent rather than fleet-wide. |
| Exploit ScenarioDerived | An attacker who is a peer on an established Soft-iWARP (siw) RDMA connection sends an extended DDP/RDMAP header deliberately fragmented so it spans more than one TCP receive callback. The second callback miscomputes the copy length, writing past the end of the header and corrupting kernel receive state (fpdu_part_rcvd); a subsequent callback then uses the resulting negative value as a copy offset to achieve an out-of-bounds kernel write, enabling memory corruption and potentially code execution. No public exploit code is known, and the attack requires control over how the header is segmented across TCP callbacks. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 07, 2026
An out-of-bounds write in the Linux kernel's siw (Soft-iWARP) RDMA driver lets a connected iWARP peer corrupt kernel memory by delivering an extended DDP/RDMAP header split across more than one TCP receive callback; the miscalculated copy length (hdrlen - MIN_DDP_HDR instead of the number of missing bytes) pushes the destination past the header, overwrites the receive state including fpdu_part_rcvd, and a later callback reuses that corrupted value as a copy offset. The upstream CVSS 3.1 vector scores this 9.8 CRITICAL (AV:N/AC:L/PR:N/UI:N/C:H/I:H/A:H), but the independent assessment rates it AV:N/AC:H (8.1) because exploitation requires the siw driver to be loaded - it is not enabled in default Linux configurations - and requires the attacker to control TCP segmentation so the header spans multiple callbacks; no authentication is needed once an RDMA session exists. Exploitation status: no public exploit identified at time of analysis, EPSS is low at 0.18% (7th percentile), and the issue is not listed in CISA KEV, though a vendor patch is available for the stable branches.
RemediationAI
Apply the vendor-released upstream fixes: kernels at or above 5.10.271, 5.15.222, 6.1.189, 6.6.158, 6.12.112, 6.18.54 and 7.2.8 (or 7.3-rc4) contain the corrected siw_get_hdr() length accounting, available from the stable tree at https://git.kernel.org/stable/c/262dcd809723723ed8a4e05437ec7e9c21a8f17e with equivalent backports at the other commits listed above; distributions should be updated to a kernel package that includes the corresponding stable release, and the advisory is tracked at https://nvd.nist.gov/vuln/detail/CVE-2026-98323 (EUVD-2026-93308). If immediate patching is not possible, the highest-value compensating control is to not have the vulnerable code path present or reachable at all: blacklist the siw module (for example an install siw /bin/false or blacklist siw directive in modprobe.d, and do not build CONFIG_RDMA_SIW), with the trade-off that Soft-iWARP over TCP is disabled entirely and any RDMA workload relying on siw will fail to establish connections. Because the driver can be loaded on demand, also ensure it is not autoloaded and verify with lsmod that it is absent. As a secondary control, restrict which hosts can reach the TCP endpoint used by the siw listener - segment the RDMA fabric and use host firewalling to allow only trusted, known iWARP peers - accepting that this reduces but does not eliminate exposure from a peer that is already permitted to connect. No user-interaction or UI-level mitigation exists since the flaw is triggered inside kernel header parsing.
Affected VersionsENISA
Affected Packages
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
siw (Soft-iWARP) implements iWARP/RDMA semantics over ordinary TCP, so protocol headers arrive as a byte stream rather than as fixed-size datagrams. siw_get_hdr() accumulates an extended DDP/RDMAP header across successive TCP receive callbacks; the bug is that after the first callback partially fills the header, the subsequent copy length is computed as hdrlen - MIN_DDP_HDR instead of the remaining (missing) byte count. The destination pointer therefore advances beyond the end of the header buffer and clobbers the receive state structure, notably fpdu_part_rcvd. On a later callback that corrupted, potentially negative fpdu_part_rcvd is used as a copy offset, producing an out-of-bounds kernel write - i.e., a length/offset validation failure of the CWE-787 (out-of-bounds write) / CWE-1284 (improper validation of specified quantity in input) class, though no CWE was supplied in the source data. The fix records how many header bytes have already been received and bounds each copy by the remaining length. Affected CPEs are generic Linux kernel entries (cpe:2.3:a:linux:linux:*:*:*:*:*:*:*:*), confirming this is a kernel-tree issue across multiple stable branches rather than a downstream product.
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
AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Network-reachable over an established siw/iWARP TCP session (AV:N, PR:N), but reliably forcing header fragmentation across callbacks and a negative offset makes it AC:H; kernel OOB write yields full C/I/A impact.
Primary rating from Vendor (Linux).
CVSS VectorVendor: Linux
Lifecycle Timeline
4DescriptionCVE.org
In the Linux kernel, the following vulnerability has been resolved:
RDMA/siw: Bound fragmented header copies by the remaining length
siw_get_hdr() can receive an extended DDP/RDMAP header across more than one TCP callback. The first callback may receive most of the header, while the next one still limits the copy to hdrlen - MIN_DDP_HDR instead of the number of missing bytes. This makes the destination move past the end of the header and overwrite the receive state, including fpdu_part_rcvd. A later callback can then use a negative fpdu_part_rcvd value as a copy offset, which creates an OOB write.
Use the number of header bytes already received when calculating the next copy length.
Executive ViewAI
A critical out-of-bounds write in the Linux kernel's siw (Soft-iWARP) RDMA driver allows a connected iWARP peer to corrupt kernel memory on any host running the module, which is not enabled in default Linux configurations but is present in RDMA-enabled server, HPC, storage, and virtualization environments. Because the flaw is remotely reachable and unauthenticated, a compromised or malicious peer on the same iWARP fabric could destabilize or take control of affected hosts, so leadership should care primarily about the availability and integrity of RDMA-dependent workloads and the potential for lateral movement across trusted fabric segments. There is currently no evidence of active exploitation, and vendor patches are available, making this a prioritized patching and configuration-review item rather than an emergency incident response.
Apply vendor patch.
Threat Intelligence Overview
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.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.
EUVD-2026-93308
GHSA-6mmc-6x3m-rgjh
NVD
CVE.org
EPSS
Exploit-DB