Skip to main content
Vulnerability Database/CVE-2026-82942

CVE-2026-82942: Apache bRPC RDMA Data Race DOS Vulnerability

CVE-2026-82942 is a data race denial of service vulnerability in Apache bRPC RDMA transport that allows remote clients to crash server processes. This post covers the technical details, affected versions, and mitigation steps.

Published:

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

CVE-2026-82942 Overview

CVE-2026-82942 is a data race vulnerability [CWE-362] in the Remote Direct Memory Access (RDMA) transport of Apache bRPC versions prior to 1.18.0. A remote, unauthenticated client can crash the server process by sending TCP data concurrently with RDMA messages after the handshake completes. The server shares its input buffer and parser state between the TCP file descriptor stream and the RDMA Queue Pair (QP) stream without synchronization. Only deployments built with BRPC_WITH_RDMA and serving rdma:// or SOCKET_MODE_RDMA sockets are affected.

Critical Impact

Unauthenticated remote attackers can crash bRPC servers that expose RDMA endpoints, producing denial of service against RPC infrastructure.

Affected Products

  • Apache bRPC versions prior to 1.18.0
  • bRPC builds compiled with the BRPC_WITH_RDMA option
  • bRPC servers accepting rdma:// or SOCKET_MODE_RDMA connections from untrusted clients

Discovery Timeline

  • 2026-10-21 - CVE-2026-82942 published to NVD
  • 2026-10-22 - Last updated in NVD database

Technical Details for CVE-2026-82942

Vulnerability Analysis

The vulnerability stems from unsynchronized sharing of socket parsing state between two concurrent I/O paths. When a bRPC server negotiates an RDMA session, the handshake completes over the underlying TCP file descriptor. The server continues to parse that TCP file descriptor as if it were still an active RPC channel after the handshake. Simultaneously, Completion Queue (CQ) events drive the RDMA QP input stream.

Both paths read into the same Socket::_read_buf and manipulate the same preferred_index and parsing_context fields. No locking or ordering guarantees prevent concurrent access. Attackers exploit this race to corrupt the parser state and trigger a server crash, resulting in denial of service.

Root Cause

Two defects combine to create the race. First, CQ event processing can begin while the handshake parsing is still in progress. Second, the handshake ACK phase can consume bytes that belong to the subsequent protocol frame. The shared _read_buf, preferred_index, and parsing_context fields are mutated by both the TCP input path and the RDMA QP input path without synchronization, violating the invariants the protocol parser relies on.

Attack Vector

A remote, unauthenticated client completes a legitimate RDMA handshake against a vulnerable bRPC server. The client then sends additional data on the TCP file descriptor while RDMA messages are concurrently being processed on the QP. The overlapping writes corrupt the shared input buffer and parser state. The parser dereferences inconsistent state, crashing the server process.

Technical details are available in the Apache bRPC GitHub Issue #3479 and the Apache mailing list disclosure thread.

Detection Methods for CVE-2026-82942

Indicators of Compromise

  • Unexpected bRPC server process crashes or segmentation faults on hosts serving rdma:// endpoints
  • Core dumps referencing Socket::_read_buf, preferred_index, or parsing_context during input parsing
  • Repeated short-lived TCP connections to RDMA-enabled bRPC ports from the same remote peer followed by server restarts

Detection Strategies

  • Inventory bRPC deployments and flag binaries compiled with BRPC_WITH_RDMA running versions below 1.18.0
  • Monitor process supervisors (systemd, Kubernetes) for abnormal restart counts on bRPC server pods and services
  • Correlate RDMA connection initiation events with subsequent TCP writes from the same peer followed by crash signals

Monitoring Recommendations

  • Enable core dump collection and symbolized stack traces for bRPC server processes to attribute crashes to this race
  • Alert on bRPC server availability drops and track SIGSEGV or SIGABRT exit codes in host telemetry
  • Log all remote peers that complete RDMA handshakes and correlate with downstream crash events for forensic review

How to Mitigate CVE-2026-82942

Immediate Actions Required

  • Upgrade Apache bRPC to version 1.18.0 or later on all servers compiled with RDMA support
  • Restrict access to RDMA-enabled bRPC endpoints to trusted network segments until patching completes
  • Audit build configurations and identify any images or packages produced with the BRPC_WITH_RDMA flag

Patch Information

Upgrade to Apache bRPC 1.18.0, which contains the fix. Operators who cannot upgrade immediately can backport the patch from Apache bRPC Pull Request #3505. The fix synchronizes access to the shared socket parsing state and prevents the TCP input path from consuming bytes after the RDMA handshake completes.

Workarounds

  • Rebuild bRPC without BRPC_WITH_RDMA if RDMA transport is not required by the workload
  • Terminate RDMA listeners and migrate affected services to TCP-only baidu_std or HTTP endpoints temporarily
  • Enforce network ACLs or firewall rules that only allow RDMA peers from authenticated internal hosts
bash
# Verify installed bRPC version and rebuild without RDMA if upgrading is not immediately feasible
git clone https://github.com/apache/brpc.git
cd brpc && git checkout 1.18.0
# Build with RDMA support enabled (patched)
cmake -B build -DWITH_RDMA=ON
cmake --build build -j

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

Experience the Most Advanced Cybersecurity Platform

See how the world’s most intelligent, autonomous cybersecurity platform can protect your organization today and into the future.