CVE-2026-64321: nvme: target: rdma: fix ndev refcount leak on queue connect

From: Greg Kroah-Hartman <[email protected]>

Description
===========

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

nvme: target: rdma: fix ndev refcount leak on queue connect

nvmet_rdma_queue_connect() calls nvmet_rdma_find_get_device() which
acquires a reference on the returned ndev via kref_get(). On the path
where the host queue backlog is exceeded and the function returns
NVME_SC_CONNECT_CTRL_BUSY, reference of ndev is not released, leaking
the kref.

Fix this by adding a goto to the existing put_device label before the
early return.

The Linux kernel CVE team has assigned CVE-2026-64321 to this issue.


Affected and fixed versions
===========================

	Issue introduced in 6.8 with commit 31deaeb11ba7a885116c9c30892b9f763c04d59c and fixed in 6.12.96 with commit d65fe42820b890a6a4644de0a95a812471f79ad3
	Issue introduced in 6.8 with commit 31deaeb11ba7a885116c9c30892b9f763c04d59c and fixed in 6.18.39 with commit a8803c4f0ac3fa7df5551bbb5a8800c434a94357
	Issue introduced in 6.8 with commit 31deaeb11ba7a885116c9c30892b9f763c04d59c and fixed in 7.1.4 with commit 5828517d17eda27f21d29ea14800c9e0a57bad11
	Issue introduced in 6.8 with commit 31deaeb11ba7a885116c9c30892b9f763c04d59c and fixed in 7.2-rc1 with commit badc53620fe813b3a9f727ef9526f98567c2c898

Please see https://www.kernel.org for a full list of currently supported
kernel versions by the kernel community.

Unaffected versions might change over time as fixes are backported to
older supported kernel versions.  The official CVE entry at
	https://cve.org/CVERecord/?id=CVE-2026-64321
will be updated if fixes are backported, please check that for the most
up to date information about this issue.


Affected files
==============

The file(s) affected by this issue are:
	drivers/nvme/target/rdma.c


Mitigation
==========

The Linux kernel CVE team recommends that you update to the latest
stable kernel version for this, and many other bugfixes.  Individual
changes are never tested alone, but rather are part of a larger kernel
release.  Cherry-picking individual commits is not recommended or
supported by the Linux kernel community at all.  If however, updating to
the latest release is impossible, the individual changes to resolve this
issue can be found at these commits:
	https://git.kernel.org/stable/c/d65fe42820b890a6a4644de0a95a812471f79ad3
	https://git.kernel.org/stable/c/a8803c4f0ac3fa7df5551bbb5a8800c434a94357
	https://git.kernel.org/stable/c/5828517d17eda27f21d29ea14800c9e0a57bad11
	https://git.kernel.org/stable/c/badc53620fe813b3a9f727ef9526f98567c2c898