Live › vulnerability › CVE-2026-82942
Go to dashboardA race between the TCP and RDMA input paths in Apache bRPC's RDMA transport corrupts a shared input buffer and parser state. A remote unauthenticated client that completed the RDMA handshake can crash the server process (denial of service).
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-23 21:57 UTC. All times on this page are UTC.
Only bRPC servers built with RDMA support (BRPC_WITH_RDMA) and serving RDMA sockets that accept connections from untrusted clients are exposed. Servers built without RDMA, or that do not negotiate RDMA, are not affected.
No product ranges from the sources yet.
grep -rn 'brpc' CMakeLists.txt or the lock file, and see whether it is below 1.18.0BRPC_WITH_RDMA and serves rdma:// or SOCKET_MODE_RDMA sockets1.18.0Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
A data race in the RDMA transport of Apache bRPC (versions < 1.18.0) allows a remote client to crash the server process (denial of service) when RDMA is enabled at build time and runtime.
Root Cause: When a bRPC server negotiates RDMA with a client, the handshake completes on the TCP fd, but the server kept parsing that fd afterwards as if it were still an RPC channel. The TCP-fd input stream and the RDMA QP input stream (driven by CQ events) shared the same Socket::_read_buf, preferred_index and parsing_context without synchronization. In addition, CQ event processing could start while the handshake parsing was still in progress, and the handshake ACK phase could consume bytes belonging to the next protocol. A remote, unauthenticated client that has completed the RDMA handshake can send data on the TCP fd at the same time RDMA messages are being processed, corrupting the shared input buffer and parser state and crashing the server process (CWE-362, availability impact).
Affected Scenarios: Use a bRPC server with RDMA support enabled (built with BRPC_WITH_RDMA and serving rdma:// / SOCKET_MODE_RDMA sockets) and accept connections from untrusted clients. Deployments without RDMA are not affected.
How to Fix: (Choose one of the following options)
This page as .md · .json · in your agent: get_signal("CVE-2026-82942")
NVD data is provided by NIST and is public domain · EPSS scores by FIRST, used with attribution. Posts quoted belong to their authors.