raid1: fix nr_pending leak in REQ_ATOMIC bad-block error path
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 5ac9e793ba2583d72740d929e7858a6c82e22ed5, Kernel 731485617bf862f1289c3f40ed1f800d0475826f and Kernel 909d9dc3b5730c8ed7b764c68bc788342df2a07b.
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
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | =6.13, >=f2a38abf5f1c5aeb3be8e9f4d3d815c867fff7ca <5ac9e793ba2583d72740d929e7858a6c82e22ed5, >=f2a38abf5f1c5aeb3be8e9f4d3d815c867fff7ca <731485617bf862f1289c3f40ed1f800d0475826f, >=f2a38abf5f1c5aeb3be8e9f4d3d815c867fff7ca <909d9dc3b5730c8ed7b764c68bc788342df2a07b | 5ac9e793ba2583d72740d929e7858a6c82e22ed5, 731485617bf862f1289c3f40ed1f800d0475826f, 909d9dc3b5730c8ed7b764c68bc788342df2a07b |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket