GPU VulnDB

Database/Kernel, userspace & hypervisor

Linux nvmet-rdma: device reference leaks whenever a queue connect is rejected as busy

CVSS 5.5CVE-2026-64321Kernel, userspace & hypervisorcurated

Impact

nvmet_rdma_queue_connect() takes a reference on the RDMA device via nvmet_rdma_find_get_device(), but the path that rejects a connect with NVME_SC_CONNECT_CTRL_BUSY returns without releasing it. Every rejected connect attempt permanently pins the device, so an initiator that repeatedly exceeds the host queue backlog drives the refcount up without bound. The practical consequence is that the RDMA device can never be released: module unload and device teardown block, and the leak is driven by the remote side rather than by anything local. On a storage target fronting an InfiniBand or RoCE fabric shared across tenants, that means the target node cannot be cleanly serviced without a reboot.

Who can reach it

Any initiator that can reach the NVMe-oF RDMA target on the storage fabric and open connections faster than the target accepts them. NVMe-oF targets are commonly exported without authentication on a trusted storage VLAN.

What to do

Update to a stable kernel carrying the fix and reboot each target node; the kernel CNA published four stable commits and no fixed version string, so match the commits below to your branch. Restricting which hosts can reach the target on the fabric limits who can drive the leak in the meantime.

References

Related entries

All Kernel, userspace & hypervisor entries

This entry is curated: imported from vendor advisories with machine assistance, not yet individually verified. Confirm against your vendor's advisory before acting, and report anything wrong.