Skip to main content
VulnerabilityPublished

CVE-2026-99714: Linux kernel · nvme: Do not drop the cdev reference twice when cdev_device_add() fails

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-99714· High

Not known to be exploited · fixed in 45d0c2d7d338ae1606984ed92d254ca0efcef921 : patch Linux kernel soon.

Data as of 20 Nov 2026, 07:34 UTC

Severity
High

Rated by Threat Radar · CVSS not yet scored by NVD

Thin evidence

One scorer or none
Patch
Available – fixed in 45d0c2d7d338ae1606984ed92d254ca0efcef921, 7dfe79db5615df8d37ae7de6d3ec099b71bf3e03, 7.3

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 20 Nov 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 19 Nov 2026.

What to do

Upgrade Linux kernel to 45d0c2d7d338ae1606984ed92d254ca0efcef921, 7dfe79db5615df8d37ae7de6d3ec099b71bf3e03 or 7.3.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • >=7.2.10 <7.3
Fixed in
  • 45d0c2d7d338ae1606984ed92d254ca0efcef921
  • 7dfe79db5615df8d37ae7de6d3ec099b71bf3e03
  • 7.3
LinuxLinuxAffected
  • =7.3
Fixed in–

Description

In the Linux kernel, the following vulnerability has been resolved: nvme: Do not drop the cdev reference twice when cdev_device_add() fails Since commit 9952f3882ecb ("nvme: fix cdev lifetime"), nvme_add_ns_cdev() and nvme_add_ns_head_cdev() take a reference to the namespace (or namespace head) before calling nvme_cdev_add(), to be dropped by the char device's release, nvme_cdev_rel(), and drop it themselves when nvme_cdev_add() fails. But when cdev_device_add() fails, nvme_cdev_add() has already put the device, and nvme_cdev_rel() has already dropped that reference: the caller drops it a second time. With one allocation failure injected into cdev_device_add() for a namespace on an NVMe over loop controller, deleting the controller gives, with native multipath: BUG: KASAN: slab-use-after-free in nvme_put_ns_head+0x21/0x140 Write of size 4 at addr ff1100000a4ea078 by task init/1 nvme_put_ns_head nvme_put_ns nvme_remove_namespaces nvme_do_delete_ctrl nvme_delete_ctrl_sync nvme_sysfs_delete Freed by task 1: kfree nvme_ns_remove nvme_remove_namespaces refcount_t: underflow; use-after-free. Take the reference in nvme_cdev_add() instead, right before cdev_device_add(), and let the callers neither take nor drop it. Add nvme_is_ns_cdev() for the check that nvme_cdev_rel() and nvme_cdev_add() now share.

References

Community reviews

Loading reviews…