md: fix soft lockup in status_resync
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel b4acb6c3ede88d6b7d33742a09e63cfce5e7fb69, Kernel 6.3.4, Kernel 6efddf1e32e2a264694766ca485a4f5e04ee82a7 and 2 more.
In the Linux kernel, the following vulnerability has been resolved: md: fix soft lockup in status_resync status_resync() will calculate 'curr_resync - recovery_active' to show user a progress bar like following: [============>........] resync = 61.4% 'curr_resync' and 'recovery_active' is updated in md_do_sync(), and status_resync() can read them concurrently, hence it's possible that 'curr_resync - recovery_active' can overflow to a huge number. In this case status_resync() will be stuck in the loop to print a large amount of '=', which will end up soft lockup. Fix the problem by setting 'resync' to MD_RESYNC_ACTIVE in this case, this way resync in progress will be reported to user.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <b4acb6c3ede88d6b7d33742a09e63cfce5e7fb69, >=6.2 <6.3.4, =2.6.12, >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <6efddf1e32e2a264694766ca485a4f5e04ee82a7, >=2.6.12.1 <6.1.30, >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <23309704e90859af2662bedc44101e6d1d2ece7e | b4acb6c3ede88d6b7d33742a09e63cfce5e7fb69, 6.3.4, 6efddf1e32e2a264694766ca485a4f5e04ee82a7, 6.1.30, 23309704e90859af2662bedc44101e6d1d2ece7e |
| linux-kernel: Kernel | >=2.6.12 <6.1.30, >=6.2.0 <6.3.4 | 6.1.30, 6.3.4 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket