Vulnerability Description
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.
References
- https://git.kernel.org/stable/c/5ac9e793ba2583d72740d929e7858a6c82e22ed5
- https://git.kernel.org/stable/c/731485617bf862f1289c3f40ed1f800d0475826f
- https://git.kernel.org/stable/c/909d9dc3b5730c8ed7b764c68bc788342df2a07b
FAQ
What is CVE-2026-74372?
CVE-2026-74372 is a documented vulnerability. 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 i...
How severe is CVE-2026-74372?
CVSS scoring is not yet available for CVE-2026-74372. Check NVD for updates.
Is there a patch for CVE-2026-74372?
Check the references section above for vendor advisories and patch information. Review vendor security bulletins for remediation guidance.