---
title: "CVE-2026-98367: Linux Kernel RDMA/siw - Use After Free"
description: "Linux kernel RDMA/siw contains a use-after-free caused by improper locking and cleanup in siw_accept and siw_qp_modify functions, letting concurrent attackers cause memory corruption, exploit requires concurrent access to QP state."
url: https://panop.io/threat-heartbeat/CVE-2026-98367/
---

# CVE-2026-98367 Linux Kernel RDMA/siw - Use After Free

Linux kernel RDMA/siw contains a use-after-free caused by improper locking and cleanup in siw\_accept and siw\_qp\_modify functions, letting concurrent attackers cause memory corruption, exploit requires concurrent access to QP state.

CVSS base score 7.8 /10

High

CISA KEV

Not listed

Public exploit

None known

EPSS

0.13% chance of exploitation in 30 days

[View the NVD record ↗](https://nvd.nist.gov/vuln/detail/CVE-2026-98367)

## Details

Type

Use After Free

Impact

Denial Of Service, Remote Code Execution

CVSS vector

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

Published

6 October 2026

Updated

15 October 2026

## Vendor fix

Update to the latest Linux kernel version containing the fix for siw\_qp\_modify and siw\_accept locking issue.

Patching closes this CVE. It does not tell you which of your systems run the affected version, or what else is exposed alongside them.

## References

- [https://nvd.nist.gov/vuln/detail/CVE-2026-98367](https://nvd.nist.gov/vuln/detail/CVE-2026-98367)
- [https://git.kernel.org/stable/c/f11e09fe2fc3a11ccdf8f932b68181b0bb1d2078](https://git.kernel.org/stable/c/f11e09fe2fc3a11ccdf8f932b68181b0bb1d2078)
- [https://git.kernel.org/stable/c/030306bbb9273af80f14d7af20129661964cd9a7](https://git.kernel.org/stable/c/030306bbb9273af80f14d7af20129661964cd9a7)
- [https://git.kernel.org/stable/c/32cd87f54dd1070020e664ccb0312a9f0fea79b4](https://git.kernel.org/stable/c/32cd87f54dd1070020e664ccb0312a9f0fea79b4)
- [https://git.kernel.org/stable/c/9dcc0f4e488b70cff81e0e5717a498c929cf5de3](https://git.kernel.org/stable/c/9dcc0f4e488b70cff81e0e5717a498c929cf5de3)
- [https://git.kernel.org/stable/c/ad50d19f3d1ce052b3a146143581e930a1efb33e](https://git.kernel.org/stable/c/ad50d19f3d1ce052b3a146143581e930a1efb33e)
- [https://git.kernel.org/stable/c/bfdc744bf20ae4c3ef2e470298de5237c5c9a13c](https://git.kernel.org/stable/c/bfdc744bf20ae4c3ef2e470298de5237c5c9a13c)
- [https://git.kernel.org/stable/c/df2584750314336edcbcc21fb388e04b260f35b7](https://git.kernel.org/stable/c/df2584750314336edcbcc21fb388e04b260f35b7)
- [https://git.kernel.org/stable/c/e3f039082856adab7e195dea1af45d93dd6a3f1c](https://git.kernel.org/stable/c/e3f039082856adab7e195dea1af45d93dd6a3f1c)

[← All CVEs](https://panop.io/threat-heartbeat/)

## What this record can't tell you

- Whether you run the affected software, and where
- Whether an attacker can actually reach and exploit it
- The misconfigurations that never get a CVE number
- What it would cost the business, ranked into what to fix first

Panop answers these inside your environment, for this CVE and every other finding.

[Book a demo](https://panop.io/demo)