CVE-2026-98352

What the bug is

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.

Where it lives

The fix touches these files. If the subsystem is one you do not use, the practical exposure is lower, though the package is still the vulnerable one.

drivers/infiniband/ulp/rtrs/rtrs-clt.c
drivers/infiniband/ulp/rtrs/rtrs-clt.h

What this is

RTRS TRANSPORT DRIVERSMAINTAINERS section matched on drivers/infiniband/ulp/rtrs/ · linux-rdma@vger.kernel.org · Maintained

Kernel module

none to look for. The file would have gone into rtrs_client, and Debian does not compile it into that module, so finding rtrs_client in lsmod would say nothing about this CVE.

Check it on the machine

grep -wE 'CONFIG_INFINIBAND|CONFIG_INFINIBAND_RTRS|CONFIG_INFINIBAND_RTRS_CLIENT' /boot/config-$(uname -r)

Reads the booted kernel's own configuration, on the machine and nowhere else. =y is built in, =m is a module, and an is not set line means the code is not there.

Show whether Debian builds this, per release

Debian does not build this code. In 4 releases below, every kernel flavour Debian publishes has the switch off, so the vulnerable file is compiled into no kernel binary Debian ships.

• bookworm, trixie, forky, sidn

n

not enabled on any flavour - this release does not build the code

Build switches

CONFIG_INFINIBAND, CONFIG_INFINIBAND_RTRS, CONFIG_INFINIBAND_RTRS_CLIENT

Reads as

all on means the file is compiled; any one off means it is not.

From the configuration Debian publishes for every kernel flavour it builds. It covers only the architectures Debian ships a linux-config package for, and nothing about a kernel you built yourself. Debian's own status above stays authoritative about the source package.MAINTAINERS kbuild Makefiles Debian linux-config packages

Signals

Published

2026-10-06 (13 days ago)source

CVSS

no vector published, unrated

Attack vector

not published

EPSS

0.17%, higher than 5.7% of all CVEssource

CISA KEV

not listedthe KEV catalogue

Debian urgency

not yet assignedsource

Subsystem

drivers/infiniband

Upstream fixes

The versions the CNA records as introducing and fixing this, and the commit for each. source

Introduced	Fixed in	Commit
5.13	5.15.222	a82cca40139d
5.13	6.1.189	74c4ed55e61f
5.13	6.6.158	6f8020fe7465
5.13	6.12.112	31024e158b45
5.13	6.18.54	8f253d5893f9
5.13	7.2.8	bf88ac486705
5.13	7.3	2ae16aaa78b5

Debian advisories