CVE-2026-98367

published 6 Oct 2026 · updated 15 Nov 2026

RDMA/siw: Clear association under lock if siw_qp_modify fails in siw_accept

7.8HighCVSS 7.8EPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel f11e09fe2fc3a11ccdf8f932b68181b0bb1d2078, Kernel 030306bbb9273af80f14d7af20129661964cd9a7, Kernel 32cd87f54dd1070020e664ccb0312a9f0fea79b4 and 12 more.

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.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
LinuxKernel>=6c52fdc244b5ccc468006fd65a504d4ee33743c7 <f11e09fe2fc3a11ccdf8f932b68181b0bb1d2078, >=6c52fdc244b5ccc468006fd65a504d4ee33743c7 <030306bbb9273af80f14d7af20129661964cd9a7, >=6c52fdc244b5ccc468006fd65a504d4ee33743c7 <32cd87f54dd1070020e664ccb0312a9f0fea79b4, >=6c52fdc244b5ccc468006fd65a504d4ee33743c7 <9dcc0f4e488b70cff81e0e5717a498c929cf5de3, >=6c52fdc244b5ccc468006fd65a504d4ee33743c7 <ad50d19f3d1ce052b3a146143581e930a1efb33e, >=6c52fdc244b5ccc468006fd65a504d4ee33743c7 <bfdc744bf20ae4c3ef2e470298de5237c5c9a13c, >=6c52fdc244b5ccc468006fd65a504d4ee33743c7 <df2584750314336edcbcc21fb388e04b260f35b7, >=6c52fdc244b5ccc468006fd65a504d4ee33743c7 <e3f039082856adab7e195dea1af45d93dd6a3f1c, =5.3f11e09fe2fc3a11ccdf8f932b68181b0bb1d2078, 030306bbb9273af80f14d7af20129661964cd9a7, 32cd87f54dd1070020e664ccb0312a9f0fea79b4, 9dcc0f4e488b70cff81e0e5717a498c929cf5de3, ad50d19f3d1ce052b3a146143581e930a1efb33e, bfdc744bf20ae4c3ef2e470298de5237c5c9a13c, df2584750314336edcbcc21fb388e04b260f35b7, e3f039082856adab7e195dea1af45d93dd6a3f1c
linux-kernel: Kernel>=5.16.0 <6.1.189, >=5.3.0 <5.10.271, >=6.13.0 <6.18.54, >=6.19.0 <7.2.8, >=6.2.0 <6.6.158, >=6.7.0 <6.12.112, >=5.11.0 <5.15.2226.1.189, 5.10.271, 6.18.54, 7.2.8, 6.6.158, 6.12.112, 5.15.222

Timeline

Every event on this vulnerability

Related

Other vulnerabilities in Kernel, strongest first

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-98367 severity on Zeptric[![CVE-2026-98367](https://zeptric.io/badge/cve/CVE-2026-98367.svg)](https://zeptric.io/cve/CVE-2026-98367)