CVE-2026-74372
Description
A flaw was found in the Linux kernel's RAID1 subsystem. When a REQ_ATOMIC write operation encounters a bad block, a reference to the RAID device (rdev) is not properly released. This resource leak prevents the affected RAID device from being removed, potentially leading to a denial of service (DoS) condition where system resources become permanently unavailable.
Statement
A moderate-severity flaw was found in the Linux kernel's md/raid1 driver, where a reference count leak occurs in the error path of a REQ_ATOMIC write that encounters a bad block. In raid1_write_request(), each per-mirror loop iteration increments rdev->nr_pending, but when a REQ_ATOMIC write finds a bad block within the requested range, the code jumps to the error handler without dropping the reference taken for the current mirror. The error handler's cleanup loop skips the current slot, leaving the nr_pending reference leaked permanently. Because raid1_remove_conf() refuses to remove an rdev with nr_pending > 0, the affected RAID device can never be removed from the array, resulting in a denial of service. Exploitation requires local write access to an md RAID1 array that supports atomic writes, and triggering depends on a REQ_ATOMIC write hitting a bad-block range. There is no impact on confidentiality or integrity; Red Hat rated this flaw Moderate (CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H, base score 5.5). In Red Hat Enterprise Linux, the vulnerable code was introduced with the md/raid1 atomic write support backport, so this flaw affects the kernel and kernel-rt packages in RHEL 9.8.z, RHEL 9.9, RHEL 10.2.z, and RHEL 10.3, and Red Hat In-Vehicle OS 2.0 and 2.1. RHEL 6, RHEL 7, RHEL 8, and the RHEL 9.2/9.4/9.6 and RHEL 10.0 update streams are not affected because the vulnerable code is not present in those releases. The fix for the affected streams is currently deferred. The residual risk of deferral is limited: exploitation requires local access and a specific bad-block condition during atomic writes, and the consequence is confined to preventing removal of the affected RAID device (a local denial of service) rather than memory exhaustion, data corruption, or privilege escalation.
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)
If an adversary can prevent a reference count from reaching zero, then resources might not be released when they are supposed to, thus causing resources to become scarce for future needs.
Availability
Technical Impact: DoS: Crash, Exit, or Restart
If an adversary can cause a reference count to reach zero when the resource is still in use, then a resource might be released before it is supposed to be, possibly forcing 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.