CVE-2026-46051
Description
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().
Predictions
Heuristic predictions, AS-IS, for prioritization only.
Mitigations
No mitigations published for this CVE yet.
The vendor-content worker queues fetches as references arrive (check back in a few minutes). Or โ if you've already worked around this in production โ publish your fix to the community-verified tier.
โ Propose a mitigation on Community โ Mitigations published via the community go through AI scoring + 2 human reviewers + 7-day silent objection window before landing here withsource_tier=community-verified.
OS impact
SUSE Affected 1 release
| Version | Status | Fixed in |
|---|---|---|
| โ | Affected | โ |
Windows Affected 1 release
| Version | Status | Fixed in |
|---|---|---|
| โ | Affected | โ |
Debian Mixed 5 releases
| Version | Status | Fixed in |
|---|---|---|
| trixie | Fixed | 6.12.86-1 |
| sid | Fixed | 7.0.4-1 |
| forky | Fixed | 7.0.4-1 |
| bullseye | Affected | โ |
| bookworm | Affected | โ |
References
- https://git.kernel.org/stable/c/09880592f5a9dc73377d6eb5ac123537b5f8df49
- https://git.kernel.org/stable/c/80fc6ca2cbde018d52e13f305edcd643911bd94b
- https://git.kernel.org/stable/c/1985cb3247e87ff6b8ca4bc5f9626f4f51024507
- https://git.kernel.org/stable/c/883cc33b7af1c448663287f069ef9dfea001e90f
- https://git.kernel.org/stable/c/7f9f7c697474268d9ef9479df3ddfe7cdcfbbffc
- https://security-tracker.debian.org/tracker/CVE-2026-46051
- https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-46051
- https://git.kernel.org/stable/c/4166d5234fe8b6c3c7f796a6c198605356c5b355
- https://git.kernel.org/stable/c/66df9f30673db66ac35145820a8e24906069ae57
- https://git.kernel.org/stable/c/a9055300e07d9d6800264d3c2560e1d0144689ca
- https://www.suse.com/security/cve/CVE-2026-46051.html
Community-verified mitigations for this CVE will appear above when contributors publish them.
Verify integrity in audit chain (admin only). AS-IS.