CVE-2026-98367: Linux kernel · RDMA/siw: Clear association under lock if siw_qp_modify fails in siw_accept
Affects Linux kernelSource CVE Database V5
Not known to be exploited · CVSS 7.8 High · fixed in f11e09fe2fc3a11ccdf8f932b68181b0bb1d2078 : patch Linux kernel soon.
Data as of 26 Oct 2026, 17:16 UTC
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 1% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in f11e09fe2fc3a11ccdf8f932b68181b0bb1d2078, e3f039082856adab7e195dea1af45d93dd6a3f1c, df2584750314336edcbcc21fb388e04b260f35b7 +5
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 6 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
AI-suggested
A fix is available and has been applied in the Linux kernel. Users should update to a fixed kernel version that includes the patches identified by the commit hashes provided. No additional mitigation is required once the system is updated.
Description
CVE-2026-98367 is a high-severity vulnerability in the Linux kernel's RDMA/siw subsystem affecting version 5.3. It involves improper handling of the association reference under a lock when siw_qp_modify fails during siw_accept, leading to a potential use-after-free condition. This occurs because the QP's state_lock is released prematurely before error cleanup, allowing a race condition that can free memory still in use.
References
- git.kernel.org/stable/c/f11e09fe2fc3a11ccdf8f932b68181b0bb1d2078 (opens in a new tab)
- git.kernel.org/stable/c/e3f039082856adab7e195dea1af45d93dd6a3f1c (opens in a new tab)
- git.kernel.org/stable/c/ad50d19f3d1ce052b3a146143581e930a1efb33e (opens in a new tab)
- git.kernel.org/stable/c/030306bbb9273af80f14d7af20129661964cd9a7 (opens in a new tab)
- git.kernel.org/stable/c/df2584750314336edcbcc21fb388e04b260f35b7 (opens in a new tab)
- git.kernel.org/stable/c/9dcc0f4e488b70cff81e0e5717a498c929cf5de3 (opens in a new tab)
- git.kernel.org/stable/c/bfdc744bf20ae4c3ef2e470298de5237c5c9a13c (opens in a new tab)
- git.kernel.org/stable/c/32cd87f54dd1070020e664ccb0312a9f0fea79b4 (opens in a new tab)