# CVE-2026-98352: RDMA/rtrs-clt: Fix CQ pool leak when connect is interrupted

> A race condition in the Linux kernel RDMA client allows a local attacker to trigger a CQ pool leak and kernel warning, causing denial of service.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 6 Oct 2026
- **Updated:** 19 Oct 2026
- **Also known as:** AZL-106173, BELL-CVE-2026-98352, DEBIAN-CVE-2026-98352, GHSA-qh4j-6f7w-8997, UBUNTU-CVE-2026-98352

## What is CVE-2026-98352?

CVE-2026-98352 is a vulnerability in Linux, published on 6 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

In the Linux kernel, the following vulnerability has been resolved:

RDMA/rtrs-clt: Fix CQ pool leak when connect is interrupted

The client borrows shared CQ credits in the ADDR_RESOLVED handler via
ib_cq_pool_get(), before the peer is connected. create_cm() can return
-ERESTARTSYS from wait_event_interruptible_timeout() without destroying
the CM ID. The init_conns() and stop-and-destroy paths then call
destroy_con_cq_qp() while cq is still NULL (no PUT) and only afterwards
rdma_destroy_id().

CMA serializes the handler against rdma_destroy_id() with handler_mutex,
but that does not order the GET against destroy_con_cq_qp(). If
ADDR_RESOLVED has already passed the DESTROYING check, it can take
con_mutex, GET credits, and then lose the con to kfree. Device
unregister later hits WARN_ON(cq->cqe_used) in ib_cq_pool_cleanup().

Set a per-connection flag under con_mutex before CQ/QP teardown so a
racing ADDR_RESOLVED cannot borrow credits after teardown has begun.

## Which versions are affected by CVE-2026-98352?


## How do I fix CVE-2026-98352?

Apply the vendor's patch.

## Is CVE-2026-98352 being exploited?

There is no known exploitation of CVE-2026-98352 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-98352 and fix it if it is affected.

What it is: CVE-2026-98352 is a vulnerability in Linux, published on 6 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-98352 in the wild and no public exploit code.

Affected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-98352/ (Markdown: https://insights.sbomify.com/CVE-2026-98352/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-98352
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-98352
- OSV: https://osv.dev/vulnerability/CVE-2026-98352

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-98352/
Summaries are generated and may contain mistakes; the official description above is the record.