Description
In the Linux kernel, the following vulnerability has been resolved:

xprtrdma: Fix ep kref imbalance on ADDR_CHANGE

rpcrdma_cm_event_handler() falls through to the disconnected: label
on RDMA_CM_EVENT_ADDR_CHANGE and calls rpcrdma_ep_put() with no
matching get when the event arrives before RDMA_CM_EVENT_ESTABLISHED.
The kref then underflows during connect teardown and
rpcrdma_xprt_disconnect() operates on a freed ep.

Reference counts across a normal connection lifecycle:

rpcrdma_ep_create() kref_init ->1
rpcrdma_xprt_connect() ep_get ->2 (before post_recvs)
RDMA_CM_EVENT_ESTABLISHED ep_get ->3
RDMA_CM_EVENT_DISCONNECTED ep_put ->2
rpcrdma_xprt_drain() ep_put ->1
rpcrdma_xprt_disconnect() tail ep_put ->0 (ep_destroy)

The connect-time get in rpcrdma_xprt_connect(), taken just before
rpcrdma_post_recvs() "while there are outstanding Receives," is
balanced by rpcrdma_xprt_drain. ADDR_CHANGE before ESTABLISHED has
no get to consume, so its put drops the count to 1 and the drain
put then frees the ep while rpcrdma_xprt_disconnect() still holds a
pointer to it.

Fix by dispatching on the prior re_connect_status via xchg(): for
prev == 0 (pre-ESTABLISHED) wake the connect waiter and return with
no put; for prev == 1 call rpcrdma_force_disconnect() and return.
The case-1 arm relies on the subsequent RDMA_CM_EVENT_DISCONNECTED
event -- reliably delivered when rdma_disconnect() is called on a
still-connected cm_id -- to balance the ESTABLISHED get;
rpcrdma_xprt_drain() continues to balance only that connect-time
get. Any other prior value means teardown is already in flight.
Published: 2026-08-15
Score: n/a
EPSS: < 1% Very Low
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Impact

The Linux kernel RPCRDMA subsystem fails to balance a reference count when an RDMA CM address change event arrives before the connection is fully established. The event handler falls through to a disconnect path and decreases the endpoint’s reference count without a corresponding increment, causing the count to underflow. When the connection tears down, the code operates on a freed endpoint object, creating a use‑after‑free condition. This flaw can lead to a kernel crash and, in the right circumstances, enable an attacker to execute arbitrary code in kernel mode.

Affected Systems

All Linux kernel builds that include the RPCRDMA module and have not applied the patch are affected. That includes mainstream distributions and custom kernels that compile or load rpcrdma, regardless of vendor or configuration, until the code fix in the public commit is included. Users of older kernel releases lacking the commit should treat their systems as vulnerable.

Risk and Exploitability

The vulnerability is a classic use‑after‑free in a privileged kernel subsystem (CWE‑416). While no EPSS score is currently available and the flaw is not listed in CISA’s KEV catalog, the severity of a kernel UAF warrants high‑risk treatment. An attacker who can manipulate or replay RDMA CM events (for instance by targeting a client or server that initiates RPCRDMA connections) could trigger the memory corruption, leading to a crash or privilege escalation. The absence of a known public exploit does not reduce the potential impact, because the conditions required for exploitation are realistic in environments that actively use RDMA connections.

Generated by OpenCVE AI on August 15, 2026 at 12:21 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Apply the latest Linux kernel release that contains the RPCRDMA reference‑count fix (e.g., commit af9b65b29af341932625c4283dc7a23cdb62688a).
  • If a kernel upgrade is not immediately possible, disable RPCRDMA support by rebuilding the kernel with CONFIG_RPCRDMA=n or by unloading the rpcrdma module so that RDMA connection handling is removed from the running system.
  • Monitor system logs for OOPS or BUG messages that reference rpcrdma or RDMA_CM_EVENT and, if such events are observed, treat them as indicators of the vulnerability and accelerate remediation.

Generated by OpenCVE AI on August 15, 2026 at 12:21 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Sat, 15 Aug 2026 06:00:00 +0000

Type Values Removed Values Added
Description In the Linux kernel, the following vulnerability has been resolved: xprtrdma: Fix ep kref imbalance on ADDR_CHANGE rpcrdma_cm_event_handler() falls through to the disconnected: label on RDMA_CM_EVENT_ADDR_CHANGE and calls rpcrdma_ep_put() with no matching get when the event arrives before RDMA_CM_EVENT_ESTABLISHED. The kref then underflows during connect teardown and rpcrdma_xprt_disconnect() operates on a freed ep. Reference counts across a normal connection lifecycle: rpcrdma_ep_create() kref_init ->1 rpcrdma_xprt_connect() ep_get ->2 (before post_recvs) RDMA_CM_EVENT_ESTABLISHED ep_get ->3 RDMA_CM_EVENT_DISCONNECTED ep_put ->2 rpcrdma_xprt_drain() ep_put ->1 rpcrdma_xprt_disconnect() tail ep_put ->0 (ep_destroy) The connect-time get in rpcrdma_xprt_connect(), taken just before rpcrdma_post_recvs() "while there are outstanding Receives," is balanced by rpcrdma_xprt_drain. ADDR_CHANGE before ESTABLISHED has no get to consume, so its put drops the count to 1 and the drain put then frees the ep while rpcrdma_xprt_disconnect() still holds a pointer to it. Fix by dispatching on the prior re_connect_status via xchg(): for prev == 0 (pre-ESTABLISHED) wake the connect waiter and return with no put; for prev == 1 call rpcrdma_force_disconnect() and return. The case-1 arm relies on the subsequent RDMA_CM_EVENT_DISCONNECTED event -- reliably delivered when rdma_disconnect() is called on a still-connected cm_id -- to balance the ESTABLISHED get; rpcrdma_xprt_drain() continues to balance only that connect-time get. Any other prior value means teardown is already in flight.
Title xprtrdma: Fix ep kref imbalance on ADDR_CHANGE
First Time appeared Linux
Linux linux Kernel
CPEs cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
Vendors & Products Linux
Linux linux Kernel
References

Subscriptions

Linux Linux Kernel
cve-icon MITRE

Status: PUBLISHED

Assigner: Linux

Published:

Updated: 2026-08-15T05:57:11.829Z

Reserved: 2026-08-09T03:40:39.934Z

Link: CVE-2026-72469

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Received

Published: 2026-08-15T06:22:20.997

Modified: 2026-08-15T06:22:20.997

Link: CVE-2026-72469

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-08-15T12:30:07Z

Weaknesses

No weakness.