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.
Affected products
Version statuses are supplied by the assigning organization. Consult the original record for detailed ranges and platform conditions.
Linux Linux
Default version status: unaffected
f2a38abf5f1c5aeb3be8e9f4d3d815c867fff7ca to < 5ac9e793ba2583d72740d929e7858a6c82e22ed5affectedf2a38abf5f1c5aeb3be8e9f4d3d815c867fff7ca to < 731485617bf862f1289c3f40ed1f800d0475826faffectedf2a38abf5f1c5aeb3be8e9f4d3d815c867fff7ca to < 909d9dc3b5730c8ed7b764c68bc788342df2a07baffected
Linux Linux
Default version status: affected
6.13affected0 to < 6.13unaffected6.18.40 to ≤ 6.18.*unaffected7.1.5 to ≤ 7.1.*unaffected7.2 to ≤ *unaffected