Bug 2516787 (CVE-2026-74372) - CVE-2026-74372 kernel: raid1: fix nr_pending leak in REQ_ATOMIC bad-block error path
Summary: CVE-2026-74372 kernel: raid1: fix nr_pending leak in REQ_ATOMIC bad-block err...
Keywords:
Status: NEW
Alias: CVE-2026-74372
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Product Security DevOps Team
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-08-15 06:33 UTC by OSIDB Bzimport
Modified: 2026-09-03 14:18 UTC (History)
2 users (show)

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


Attachments (Terms of Use)

Description OSIDB Bzimport 2026-08-15 06:33:28 UTC
In the Linux kernel, the following vulnerability has been resolved:

raid1: fix nr_pending leak in REQ_ATOMIC bad-block error path

In raid1_write_request(), each per-mirror loop iteration begins by
incrementing rdev->nr_pending. If a REQ_ATOMIC write encounters a
badblock within the requested range, the code jumps to err_handle
without dropping the reference taken for the current mirror.

err_handle's cleanup loop will only decrements for k < i and
r1_bio->bios[k] is non-NULL. The current slot is therefore skipped,
leaving its nr_pending reference leaked permanently. The reference
prevents the rdev from ever being removed, since raid1_remove_conf()
refuses to remove an rdev with nr_pending > 0.

Fix this by calling rdev_dec_pending() before jumping to err_handle.


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