Linux
xprtrdma: Fix ep kref imbalance on ADDR_CHANGE
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.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- >= 2acc5cae292355f5f18ad377a2a966e7f03c8fec, < a562485c359d0b20a99d466b042af9c2f7ff3326
- >= 2acc5cae292355f5f18ad377a2a966e7f03c8fec, < cfd1bab66b042da7a778786685125656c695931b
- >= 2acc5cae292355f5f18ad377a2a966e7f03c8fec, < d0479c2b12974aa188b10d221a5770126b118b6d
- >= 2acc5cae292355f5f18ad377a2a966e7f03c8fec, < ffc07790539736a5d029f6a3c966b46c529f93a8
- >= 2acc5cae292355f5f18ad377a2a966e7f03c8fec, < af9b65b29af341932625c4283dc7a23cdb62688a
- 2fcbf07a4f23174a45e015b62a8e42ddbc2e53ef
- >= 5.7.9, < 5.8
Fixed in a562485c359d0b20a99d466b042af9c2f7ff3326, cfd1bab66b042da7a778786685125656c695931b, d0479c2b12974aa188b10d221a5770126b118b6d, ffc07790539736a5d029f6a3c966b46c529f93a8, af9b65b29af341932625c4283dc7a23cdb62688a, 5.8
- 5.8
Fixed in 0, 6.6.160, 6.12.97, 6.18.40, 7.1.5, 7.2
Mitigation
Upgrade Linux to a562485c359d0b20a99d466b042af9c2f7ff3326 or cfd1bab66b042da7a778786685125656c695931b or d0479c2b12974aa188b10d221a5770126b118b6d or ffc07790539736a5d029f6a3c966b46c529f93a8 or af9b65b29af341932625c4283dc7a23cdb62688a or 5.8 or later.
Upgrade Linux to 0 or 6.6.160 or 6.12.97 or 6.18.40 or 7.1.5 or 7.2 or later.
Timeline
Days relative to CVE publicationNo public PoC found yet; not in CISA KEV.
PoC repositories
Found on GitHub.No PoC repositories found yet.