Bug 2535140 (CVE-2026-89972) - CVE-2026-89972 kernel: nvme: add missing SRCU grace period in error path
Summary: CVE-2026-89972 kernel: nvme: add missing SRCU grace period in error path
Keywords:
Status: NEW
Alias: CVE-2026-89972
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
high
high
Target Milestone: ---
Assignee: Product Security DevOps Team
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-09-16 10:58 UTC by OSIDB Bzimport
Modified: 2026-10-08 09:50 UTC (History)
17 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2026:75746 0 None None None 2026-10-05 10:48:58 UTC
Red Hat Product Errata RHSA-2026:75747 0 None None None 2026-10-05 11:24:08 UTC
Red Hat Product Errata RHSA-2026:76738 0 None None None 2026-10-07 20:28:52 UTC
Red Hat Product Errata RHSA-2026:76739 0 None None None 2026-10-08 09:50:33 UTC

Description OSIDB Bzimport 2026-09-16 10:58:13 UTC
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.

Comment 3 Jon Orris 2026-10-05 10:48:57 UTC
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 8

Via RHSA-2026:75746 https://access.redhat.com/errata/RHSA-2026:75746

Comment 4 Jon Orris 2026-10-05 11:24:06 UTC
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 8

Via RHSA-2026:75747 https://access.redhat.com/errata/RHSA-2026:75747

Comment 5 Jon Orris 2026-10-07 20:28:50 UTC
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 10

Via RHSA-2026:76738 https://access.redhat.com/errata/RHSA-2026:76738

Comment 6 Jon Orris 2026-10-08 09:50:32 UTC
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 9

Via RHSA-2026:76739 https://access.redhat.com/errata/RHSA-2026:76739


Note You need to log in before you can comment on or make changes to this bug.