KernelScan.io

HIGH Introduced in 5.3

siw QpModify UAF

CVE-2026-98367

CVSS 7.8 / 10.0 NVD

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

KernelScan AI7.0HIGH

01

In the Linux kernel, the following vulnerability has been resolved: RDMA/siw: Clear association under lock if siw_qp_modify fails in siw_accept We need to clear cep before release state_lock as siw_qp_llp_close and siw_qp_modify->siw_qp_llp_close did. Otherwise if siw_qp_modify() fails in siw_accept(), the QP's state_lock is released before the error path cleanup. A concurrent ibv_modify_qp() transitioning the QP to ERROR can race in this window: siw_accept() ibv_modify_qp(ERROR) ---------------------- ---------------------- siw_qp_modify() fails up_write(&qp->state_lock) down_write(&qp->state_lock) nextstate_from_idle(): if (qp->cep) siw_cep_put(qp->cep) <- frees cep qp->cep = NULL goto error cep->qp = NULL <- UAF Clear qp->cep and drop the association reference taken by siw_cep_get(), all under the write lock held from the initial down_write(&qp->state_lock). Thread B therefore sees qp->cep == NULL, skips its own put, and cannot free the cep before siw_accept() is done with it.

02

Engine v0.7.0

Risk summary

A local attacker with access to RDMA devices can exploit a race condition in the SIW software iWarp driver to trigger a use-after-free on a connection endpoint object, potentially achieving kernel code execution or causing a system crash. The vulnerability requires the SIW kernel module to be loaded and precise timing of two concurrent RDMA operations.

Affecteddrivers/infiniband/sw/siw/siw_cm.c (RDMA SIW connection management)

Vulnerability analysis

In the software iWarp RDMA driver, when an internal state change fails while accepting a connection, the driver releases its synchronization too early, before removing the link between the connection and its endpoint object. A concurrent thread trying to tear down the same connection can run in this gap, find the endpoint still linked, drop its reference count (potentially freeing it), and then the original thread accesses the already-freed endpoint — a use-after-free. The fix removes the link and drops the reference before releasing the synchronization, so the concurrent thread sees no endpoint to clean up and cannot free it prematurely. This is reachable by local processes with access to RDMA device files, requires the software iWarp driver to be active, and demands precise timing of two concurrent RDMA operations.

03

BranchIntroducedFixed inPatch commit
5.105.35.10.271f11e09fe2fc3
5.155.35.15.222e3f039082856
6.15.36.1.189ad50d19f3d1c
6.125.36.12.112df2584750314
6.185.36.18.549dcc0f4e488b
6.65.36.6.158030306bbb927
7.25.37.2.8bfdc744bf20a
mainline5.37.332cd87f54dd1
cip/5.105.35.10.271-cip78f11e09fe2fc3
cip/5.10-rt5.35.10.272-cip79-rt35f11e09fe2fc3
cip/6.15.36.1.189-cip61ad50d19f3d1c
cip/6.1-rt5.36.1.189-cip61-rt32ad50d19f3d1c
cip/6.125.36.12.112-cip33df2584750314

04

State of the newest release of each Civil Infrastructure Platform SLTS tree, from CIP's own fix records.

CIP treeState
cip/6.12Fixed in 6.12.112-cip33
cip/6.1Fixed in 6.1.189-cip61
cip/6.1-rtFixed in 6.1.189-cip61-rt32
cip/5.10Fixed in 5.10.271-cip78
cip/5.10-rtFixed in 5.10.272-cip79-rt35