Skip to main content
VulnerabilityPublished Updated

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

Affects Linux kernelSource CVE Database V5

0
Compare

Not known to be exploited · fixed in d65fe42820b890a6a4644de0a95a812471f79ad3 : update Linux kernel when convenient.

Data as of 6 Nov 2026, 17:04 UTC

Severity
Unrated

Rated by Threat Radar · No CVSS score from NVD or the CNA

Thin evidence

One scorer or none
CISA SSVC
Exploitation
No evidence of active exploitation and no public proof of concept
Automatable
Attackers cannot reliably automate steps 1–4 of the kill chain
Technical impact
Limited control over the software or limited information exposure

CISA SSVC assessment, 2026-11-06.

Patch
Available – fixed in d65fe42820b890a6a4644de0a95a812471f79ad3, badc53620fe813b3a9f727ef9526f98567c2c898, a8803c4f0ac3fa7df5551bbb5a8800c434a94357 +4

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 25 Jul 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 6 Nov 2026.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ 31deaeb11ba7a885116c9c30892b9f763c04d59c, < d65fe42820b890a6a4644de0a95a812471f79ad3
Fixed in
  • d65fe42820b890a6a4644de0a95a812471f79ad3
LinuxLinuxAffected
  • ≥ 31deaeb11ba7a885116c9c30892b9f763c04d59c, < badc53620fe813b3a9f727ef9526f98567c2c898
Fixed in
  • badc53620fe813b3a9f727ef9526f98567c2c898
LinuxLinuxAffected
  • ≥ 31deaeb11ba7a885116c9c30892b9f763c04d59c, < a8803c4f0ac3fa7df5551bbb5a8800c434a94357
Fixed in
  • a8803c4f0ac3fa7df5551bbb5a8800c434a94357
LinuxLinuxAffected
  • ≥ 31deaeb11ba7a885116c9c30892b9f763c04d59c, < 5828517d17eda27f21d29ea14800c9e0a57bad11
Fixed in
  • 5828517d17eda27f21d29ea14800c9e0a57bad11
LinuxLinuxAffected
  • ≥ 85a79da286b65ae2238a22ac901a0039779e613e, < 712f3268a62d0df98a7ee991cba963ced2e58007
Fixed in
  • 712f3268a62d0df98a7ee991cba963ced2e58007
LinuxLinuxAffected
  • ≥ 28877977bbc4f44dd3068b74ee781466c597a3b3, < 204b9645536bb4a77a2cb35e6519dbf9f4ea1665
Fixed in
  • 204b9645536bb4a77a2cb35e6519dbf9f4ea1665

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.

References

Community reviews

Loading reviews…