External risk intelligence

Linux Kernel RDMA Out-of-Bounds Write Vulnerability

CVE advisorySeverity: CRITICAL (CVSS 9.8)

CVE-2026-64268

The vulnerability affects RDMA over iWARP in the Linux kernel. While iWARP is routable over TCP, RDMA deployments are typically restricted to high-performance computing, data center interconnects, or specialized storage networks. Public internet exposure of RDMA-enabled interfaces is uncommon, as these protocols are generally isolated within private infrastructure and internal network segments.

Halo Surface Signal: 2 out of 5 — less likely to be public-facing.

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

A vulnerability in the Linux kernel's RDMA/siw component could allow an attacker to write data beyond a buffer's boundaries, potentially leading to a system crash or data corruption. This issue arises from how the system handles incoming read responses and their placement within memory.

  • Remote attackers can exploit this Linux kernel flaw.
  • Key concern is confirming relevance and exposure within networks.
  • Understand potential impact and verify system relevance.

Attack Path

How an attacker could exploit the issue

An attacker can compromise systems by sending specially crafted RDMA Read Response segments. This occurs when an established RDMA connection is abused to send responses that exceed the requested data length. The vulnerability in the Linux kernel's RDMA subsystem then leads to data being written outside of its intended buffer.

  • Requires an established RDMA connection.
  • Triggered by oversized Read Response segments.
  • Allows out-of-bounds writes.

Live Threat

Current exploitation, exposure, and threat context

When supported by the advisory, an unauthenticated, remote attacker could exploit this vulnerability to cause a buffer overread. This could affect system memory and potentially lead to denial of service or information disclosure.

  • System memory could be affected.
  • Remote peer writes out of bounds.
  • Potential for denial of service or disclosure.

Operational Fix

Recommended remediation, mitigation, and detection steps

This vulnerability in the Linux kernel's RDMA/siw driver could be exploited by a remote attacker without local privilege. Ownership likely falls to the platform or infrastructure teams managing the kernel and RDMA implementations, in coordination with network and security teams responsible for network exposure. The first practical step is to identify all systems utilizing RDMA/siw, assess their network reachability and business criticality, and then assign an accountable owner for remediation planning.

  • Platform/Infrastructure teams own the issue.
  • Verify RDMA/siw deployment and exposure.
  • Plan remediation based on assessed risk.

Supplementary metadata

Validate whether this threat affects your internet-facing exposure.

Halo Threat Intelligence helps prioritize remediation with Halo Surface Signal and H/A/L/O context. Start exposure validation with a free external attack surface trial.

Frequently asked questions

What is the Linux RDMA/siw component?

The RDMA/siw component is the software implementation of the iWARP protocol within the Linux kernel. It allows computers to perform Remote Direct Memory Access (RDMA) over standard TCP/IP networks. This technology is typically used in high-performance computing, data center interconnects, and specialized storage networks to enable fast data transfer directly between system memories without heavy CPU involvement.

How does CVE-2026-64268 work?

This vulnerability is an out-of-bounds write flaw. It occurs because the software fails to check if the total amount of incoming data matches the length of the destination buffer when processing multi-segment RDMA Read Responses. An attacker can send specially crafted segments that keep the data stream open, causing the system to write data past the end of the intended memory area.

What triggers this RDMA vulnerability?

The vulnerability is triggered when a remote peer on an established RDMA connection sends a sequence of Read Response segments that carry more total payload than originally requested. The bug is not triggered by standard, correctly sized traffic, nor does it require the attacker to have any local login privileges on the target system to initiate the exploitation attempt.

Is my network affected by CVE-2026-64268?

Halo Surface Signal indicates that exploitation is unlikely for most organizations because RDMA-enabled interfaces are rarely exposed to the public internet. While iWARP is technically routable over TCP, these protocols are almost always isolated within internal network segments or private data center infrastructure, limiting the reach of potential remote attackers.

How should I respond to this kernel issue?

Your first step is to perform an inventory to identify all systems in your environment that currently utilize the RDMA/siw driver. Once identified, work with your infrastructure teams to assess the network reachability of these systems and determine their business criticality. Use this information to prioritize kernel updates or configuration changes according to your organization's patch management lifecycle.

References