Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-89972

nvme: add missing SRCU grace period in error path

Description

In the Linux kernel, the following vulnerability has been resolved: nvme: add missing SRCU grace period in error path nvme_alloc_ns() error path at out_unlink_ns removes ns from the namespace head siblings list with list_del_rcu(&ns->siblings) but does not wait for SRCU readers before freeing the namespace struct. Multipath code iterates the head->list under srcu_read_lock() in nvme_find_path() and nvme_mpath_revalidate_paths(), so a concurrent reader can still hold a reference to ns when kfree(ns) runs. The normal removal path in nvme_ns_remove() correctly calls synchronize_srcu(&ns->head->srcu) after list_del_rcu() to wait for in-progress readers. Add the same grace period in the error path.

Timeline

  1. ID reserved

    By Linux

  2. · 5 days later

    Published

  3. · 44 days later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2026-89972, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1Critical9.8CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
NVDNVD · Received3.1Critical9.8CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS (exploitation in 30 days)
0.76% · top 44% of all CVEs (12 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Critical 9.8.

Affected products

  • Linux · Linux

    • affected ed754e5deeb17f4e675c84e4b6c640cc7344e498 – < 037e71058e8a59568db72015d4386f54e54dff77
    • affected ed754e5deeb17f4e675c84e4b6c640cc7344e498 – < 7f180cef9f3421ece85c43bfdc326ce5875845bb
    • affected ed754e5deeb17f4e675c84e4b6c640cc7344e498 – < da710ec2a70a85de73afd4f7869b234fd9ede49e
    • affected ed754e5deeb17f4e675c84e4b6c640cc7344e498 – < 3868476cd39161f18720582df17a1b621e805b5d
    • affected ed754e5deeb17f4e675c84e4b6c640cc7344e498 – < 0d4735418512ef825176726eaaa8bd6a35f6b46d
    • affected ed754e5deeb17f4e675c84e4b6c640cc7344e498 – < d663944dbad81bb0e3635d7090db4713e6300858
    • affected ed754e5deeb17f4e675c84e4b6c640cc7344e498 – < 76023560d60f10b4f808941163aa2975f1631683
    • affected ed754e5deeb17f4e675c84e4b6c640cc7344e498 – < ef248d5de4469fb6bbaf8dbe0c4c47800080d648
  • Linux · Linux

    • affected 4.15
    • unaffected < 4.15
    • unaffected 5.10.273 – ≤ 5.10.*
    • unaffected 5.15.224 – ≤ 5.15.*
    • unaffected 6.1.191 – ≤ 6.1.*
    • unaffected 6.6.160 – ≤ 6.6.*
    • unaffected 6.12.112 – ≤ 6.12.*
    • unaffected 6.18.51 – ≤ 6.18.*
    • unaffected 7.2.5 – ≤ 7.2.*
    • unaffected 7.3 – ≤ *

References

References8

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-89972 badge
[![CVE-2026-89972](https://cveledger.app/badge/CVE-2026-89972.svg)](https://cveledger.app/cve/CVE-2026-89972)

Record last updated .