CVE-2026-99597

Description

A flaw was found in the Linux kernel's Sleepable Read-Copy Update (SRCU) mechanism. When splicing SRCU-protected lists, the kernel improperly synchronizes list entries by waiting for standard Read-Copy Update (RCU) readers instead of SRCU readers. This allows active readers to continue accessing list entries while pointers are concurrently modified. Consequently, concurrent operations can trigger a race condition, potentially leading to memory corruption or a Denial of Service (DoS) via a system crash.

Statement

This vulnerability is rated as having Moderate impact because successful exploitation requires local administrative privileges, precise synchronization timing, and specifically targets storage namespace teardown paths. In standard Red Hat Enterprise Linux deployments, invoking this synchronization flaw in the kernel's read-copy-update subsystem demands root access to initiate hardware or namespace removal operations. Consequently, an attacker cannot exploit this flaw remotely or without elevated access, constraining the potential impact to a localized denial of service via a system crash.

Common Vulnerability Scoring System (CVSS) Score Details

Info alert:Important note

CVSS scores for open source components depend on vendor-specific factors (e.g. version or build chain). Therefore, Red Hat's score and impact rating can be different from NVD and other vendors. Red Hat remains the authoritative CVE Naming Authority (CNA) source for its products and services (see Red Hat classifications).

The following CVSS metrics and score provided are preliminary and subject to review.

CVSS v3 Score Breakdown

Red HatNVDcve.org
Base Score4.1N/AN/A
Attack VectorLocalN/AN/A
Attack ComplexityHighN/AN/A
Privileges RequiredHighN/AN/A
User InteractionNoneN/AN/A
ScopeUnchangedN/AN/A
ConfidentialityNoneN/AN/A
Integrity ImpactNoneN/AN/A
Availability ImpactHighN/AN/A

Vector

Red Hat: CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:U/C:N/I:N/A:H

Understanding the Weakness (CWE)

Integrity,Confidentiality,Other

Technical Impact: Modify Application Data; Read Application Data; Alter Execution Logic; Unexpected State

If access to a shared resource is not correctly synchronized, then the resource may not be in a state that is expected by the product. This might lead to unexpected or insecure behaviors, especially if an attacker can influence the shared resource.

Frequently Asked Questions

Want to get errata notifications? Sign up here.