md/raid5: fix soft lockup in retry_aligned_read()
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 5.10.258, 5.15.209, 6.1.175, 6.6.140, 6.12.86, and 2 more
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
In the Linux kernel, the following vulnerability has been resolved: md/raid5: fix soft lockup in retry_aligned_read() When retry_aligned_read() encounters an overlapped stripe, it releases the stripe via raid5_release_stripe() which puts it on the lockless released_stripes llist. In the next raid5d loop iteration, release_stripe_list() drains the stripe onto handle_list (since STRIPE_HANDLE is set by the original IO), but retry_aligned_read() runs before handle_active_stripes() and removes the stripe from handle_list via find_get_stripe() -> list_del_init(). This prevents handle_stripe() from ever processing the stripe to resolve the overlap, causing an infinite loop and soft lockup. Fix this by using __release_stripe() with temp_inactive_list instead of raid5_release_stripe() in the failure path, so the stripe does not go through the released_stripes llist. This allows raid5d to break out of its loop, and the overlap will be resolved when the stripe is eventually processed by handle_stripe().
Timeline
- CVE published
- Record last updated
Affected versions
- Linux Linux
From 773ca82fa1ee58dd1bf88b6a5ca385ec83a2cac6 · fixed in 66df9f30673db66ac35145820a8e24906069ae57; From 773ca82fa1ee58dd1bf88b6a5ca385ec83a2cac6 · fixed in 4166d5234fe8b6c3c7f796a6c198605356c5b355; From 773ca82fa1ee58dd1bf88b6a5ca385ec83a2cac6 · fixed in a9055300e07d9d6800264d3c2560e1d0144689ca; From 773ca82fa1ee58dd1bf88b6a5ca385ec83a2cac6 · fixed in 09880592f5a9dc73377d6eb5ac123537b5f8df49; From 773ca82fa1ee58dd1bf88b6a5ca385ec83a2cac6 · fixed in 80fc6ca2cbde018d52e13f305edcd643911bd94b; From 773ca82fa1ee58dd1bf88b6a5ca385ec83a2cac6 · fixed in 1985cb3247e87ff6b8ca4bc5f9626f4f51024507; From 773ca82fa1ee58dd1bf88b6a5ca385ec83a2cac6 · fixed in 883cc33b7af1c448663287f069ef9dfea001e90f; From 773ca82fa1ee58dd1bf88b6a5ca385ec83a2cac6 · fixed in 7f9f7c697474268d9ef9479df3ddfe7cdcfbbffc
- Linux Linux
3.12
- KernelLinux
From 3.12.0 · fixed in 5.10.258; From 5.11.0 · fixed in 5.15.209; From 5.16.0 · fixed in 6.1.175; From 6.2.0 · fixed in 6.6.140; From 6.7.0 · fixed in 6.12.86; From 6.13.0 · fixed in 6.18.27; From 6.19.0 · fixed in 7.0.4
References 8
git.kernel.org
- stable/c/66df9f30673db66ac35145820a8e24906069ae57
- stable/c/4166d5234fe8b6c3c7f796a6c198605356c5b355
- stable/c/a9055300e07d9d6800264d3c2560e1d0144689ca
- stable/c/09880592f5a9dc73377d6eb5ac123537b5f8df49
- stable/c/80fc6ca2cbde018d52e13f305edcd643911bd94b
- stable/c/1985cb3247e87ff6b8ca4bc5f9626f4f51024507
- stable/c/883cc33b7af1c448663287f069ef9dfea001e90f
- stable/c/7f9f7c697474268d9ef9479df3ddfe7cdcfbbffc