CVE-2026-72439
Description
A flaw was found in the Linux kernel's md/raid10 component. When write requests fail, the raid10_write_request() function may not properly release a writes_pending reference. This resource leak can accumulate over time, potentially leading to a denial of service (DoS) condition where the system becomes unresponsive or crashes.
Statement
A flaw was found in the Linux kernel's md/raid10 driver, affecting the kernel and kernel-rt packages in Red Hat Enterprise Linux 8, 9, and 10 as well as the kernels shipped in Red Hat In-Vehicle OS 2; Red Hat rates the impact of this flaw as Low. raid10_make_request() acquires a writes_pending reference with md_write_start() before dispatching write requests, but several failure paths in raid10_write_request() complete the bio and return without reaching the normal write completion path, so the corresponding md_write_end() is skipped. Each such failed write request leaks a writes_pending reference, leaving the RAID10 array with a permanently elevated pending-write count; later operations that wait for writes to drain, such as array management or recovery operations, may then hang, resulting in a local denial of service. Exploitation requires local write access to a filesystem or block device backed by an affected RAID10 array and a code path in which a write request fails. While the CVSS:3.1 availability-only vector (AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H) scores 5.5 (Moderate), Red Hat's Low impact rating reflects that triggering the leak requires a specific md/raid10 configuration combined with write request failures, and no confidentiality or integrity impact exists. Red Hat Enterprise Linux 7 and the RHEL 8.4 and 8.6 update streams are not affected because the vulnerable code, introduced with the raid10 nowait support, is not present in those kernels. As the flaw is rated Low impact, fixes for the affected streams are deferred to future scheduled kernel updates rather than immediate z-stream updates; the residual risk is a local denial of service limited to systems with affected md/raid10 arrays where write requests fail.
Mitigation
Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability.
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 Hat | NVD | cve.org | |
|---|---|---|---|
| Base Score | 5.5 | N/A | N/A |
| Attack Vector | Local | N/A | N/A |
| Attack Complexity | Low | N/A | N/A |
| Privileges Required | Low | N/A | N/A |
| User Interaction | None | N/A | N/A |
| Scope | Unchanged | N/A | N/A |
| Confidentiality | None | N/A | N/A |
| Integrity Impact | None | N/A | N/A |
| Availability Impact | High | N/A | N/A |
Vector
Red Hat: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Understanding the Weakness (CWE)
Availability
Technical Impact: DoS: Resource Consumption (Memory); DoS: Resource Consumption (Other)
An adversary that can cause a resource counter to become inaccurate may be able to create situations where resources are not accounted for and not released, thus causing resources to become scarce for future needs.
Availability
Technical Impact: DoS: Crash, Exit, or Restart
An adversary that can cause a resource counter to become inaccurate may be able to force an error that causes the product to crash or exit out of its current operation.
Frequently Asked Questions
Not sure what something means? Check out our Security Glossary.
Want to get errata notifications? Sign up here.