Skip to main content

CVE-2026-99714Linux vulnerability

Low priorityNot scoredEPSS not scored yet

CVE-2026-99714 is a vulnerability in Linux, not yet scored.

Why this priority: Not scored yet, and no exploitation signal.

Published · Updated · NVD status: Received

What it is

The record does not classify the weakness yet; the description below says what the reporter found.

How it is reached

The record does not say yet how the flaw is reached; the description below is the best guide until it is scored.

What an attacker gains

Its impact has not been scored yet.

Is it being exploited?

There is no public report of exploitation yet.

What to do

  1. Upgrade Linux to a fixed version for your release line (7.3, 7.3.5, 7.4-rc2).

Description from NVD

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.

What this means for your architecture.

A CVE names a product. Whether it matters depends on where that product sits in your systems: what reaches it, which trust boundary it guards and what it can reach once compromised. Veriom maps your components, their relationships and your trust boundaries from your code, cloud and delivery evidence, so you can see where a component like this sits. The radar itself does not look at your systems.

Components it touches

  • Linux. Start from where it runs and what it is connected to.

Trust boundaries in play

    Questions to answer about your own systems

    • Where does Linux run in your systems, and at which version?
    • Which of those instances are reachable by people you do not trust?
    • What can it reach once compromised: which data stores, secrets and services?

    14-day free trial

    Understand how your systems connect.

    See your services, dependencies and trust boundaries in one place, with evidence from your connected environment.

    Sources

    • CVE records and CVSS scores from the NVD CVE API. This product uses the NVD API but is not endorsed or certified by the NVD.
    • Exploitation status from CISA’s Known Exploited Vulnerabilities catalog.
    • Exploit likelihood from FIRST’s Exploit Prediction Scoring System (EPSS), refreshed daily.
    • Explanations are written by Veriom from fixed templates over each record’s data, not by a person reviewing each CVE. Descriptions are quoted from the records as published.