From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-alma10-1.taild15c8.ts.net [100.103.45.18]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 113E740756F for ; Wed, 27 May 2026 13:03:27 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=100.103.45.18 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1779887008; cv=none; b=nHtj/eN14L2NGF9icg/Hy/x9De0GYrPucHo5N/tDrR+5ubd/0t0TOlJT/LGO9P68hF8LICDAIErIeuta/pNqirhzdWDMu03P0gJs0cX6hPyM0e4HivlSnPLdB3ef5bUibxYuTgr0oohfHEUN/j4ZT87K48y/9bY4qysyT3f2pTs= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1779887008; c=relaxed/simple; bh=aQ3A2fDTvrBQjh+vf5IH3TonZn5ZWafcd+0ZBuMaye0=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version; b=P1eWtVvxoSmw00If0JPFw3EdcJAFNaOsLBi54eYRJZTYfcgx0YJp8YxrQn08rugQZKuPw5gHXJIV5mAwOznHR5NxYoKJa132x660iIAqZ74RLICWb0DQnEz5rlURrRO7i1D5uAbzwwEM1WHgKo2M65X/8vKrst2vHcpcN+Ybsb0= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.b=J3+3upXC; arc=none smtp.client-ip=100.103.45.18 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.b="J3+3upXC" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 512E01F000E9; Wed, 27 May 2026 13:03:26 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linuxfoundation.org; s=korg; t=1779887006; bh=vUe8jpWHsE8iaOP9ZcoZD9N7NomCUrQQq0o1gtTbbrM=; h=From:To:Cc:Subject:Date:Reply-To; b=J3+3upXCuMTgAhvYRq9JksXKyRncVozaO3uEpnJVa6uyQqYU7HA5ST+gipskAoPY3 XDg2y0LXvauJUPkzoH0wFjy7dhHYCCwYde0M2YSvWR5/huT6mZT5ARpsr8Wt/Y58oT HveDK9eki3R4r7UOD48ZJh8Dr81wRlDxe6KOiPoI= From: Greg Kroah-Hartman To: linux-cve-announce@vger.kernel.org Cc: Greg Kroah-Hartman Subject: CVE-2026-46051: md/raid5: fix soft lockup in retry_aligned_read() Date: Wed, 27 May 2026 14:59:42 +0200 Message-ID: <2026052753-CVE-2026-46051-e465@gregkh> X-Mailer: git-send-email 2.54.0 Reply-To: , Precedence: bulk X-Mailing-List: linux-cve-announce@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 X-Developer-Signature: v=1; a=openpgp-sha256; l=3345; i=gregkh@linuxfoundation.org; h=from:subject:message-id; bh=lV9tSW4se1Rvq+xPyMajhp5D7gORVp30K0dibE/ez0M=; b=owGbwMvMwCRo6H6F97bub03G02pJDFlir3q3r7Lst5dID88pfqYl7tBg7CMiH85cNrd4W6pdr a/GkrKOWBYGQSYGWTFFli/beI7urzik6GVoexpmDisTyBAGLk4BmEjOdIb59bYluWZnPDMTjU4X /Yjov5fooR/KsKB5UvJxkYNzL1SY1N07tixRpf/B/TkA X-Developer-Key: i=gregkh@linuxfoundation.org; a=openpgp; fpr=F4B60CC5BF78C2214A313DCB3147D40DDB2DFB29 Content-Transfer-Encoding: 8bit From: Greg Kroah-Hartman 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(). The Linux kernel CVE team has assigned CVE-2026-46051 to this issue. Affected and fixed versions =========================== Issue introduced in 3.12 with commit 773ca82fa1ee58dd1bf88b6a5ca385ec83a2cac6 and fixed in 6.6.140 with commit 09880592f5a9dc73377d6eb5ac123537b5f8df49 Issue introduced in 3.12 with commit 773ca82fa1ee58dd1bf88b6a5ca385ec83a2cac6 and fixed in 6.12.86 with commit 80fc6ca2cbde018d52e13f305edcd643911bd94b Issue introduced in 3.12 with commit 773ca82fa1ee58dd1bf88b6a5ca385ec83a2cac6 and fixed in 6.18.27 with commit 1985cb3247e87ff6b8ca4bc5f9626f4f51024507 Issue introduced in 3.12 with commit 773ca82fa1ee58dd1bf88b6a5ca385ec83a2cac6 and fixed in 7.0.4 with commit 883cc33b7af1c448663287f069ef9dfea001e90f Issue introduced in 3.12 with commit 773ca82fa1ee58dd1bf88b6a5ca385ec83a2cac6 and fixed in 7.1-rc1 with commit 7f9f7c697474268d9ef9479df3ddfe7cdcfbbffc Please see https://www.kernel.org for a full list of currently supported kernel versions by the kernel community. Unaffected versions might change over time as fixes are backported to older supported kernel versions. The official CVE entry at https://cve.org/CVERecord/?id=CVE-2026-46051 will be updated if fixes are backported, please check that for the most up to date information about this issue. Affected files ============== The file(s) affected by this issue are: drivers/md/raid5.c Mitigation ========== The Linux kernel CVE team recommends that you update to the latest stable kernel version for this, and many other bugfixes. Individual changes are never tested alone, but rather are part of a larger kernel release. Cherry-picking individual commits is not recommended or supported by the Linux kernel community at all. If however, updating to the latest release is impossible, the individual changes to resolve this issue can be found at these commits: 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