Menu

Star on GitHub · 3.2k

CVE-2026-64321

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…

Published Jul 25, 2026EPSS 0.12%

Overview

CVE-2026-64321 is a known-severity vulnerability. It was published on July 25, 2026.

Technical 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.

Remediation

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

Frequently asked questions

What is CVE-2026-64321?

CVE-2026-64321 is a known-severity vulnerability. It was published on July 25, 2026.

How severe is CVE-2026-64321?

CVSS score information is not yet available for this vulnerability. Check back as the CVE record is updated by NVD analysts.

How do I fix or remediate CVE-2026-64321?

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2026-64321?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2026-64321 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.