From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-1.web.codeaurora.org [10.30.226.201]) (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 5FFED21C190 for ; Wed, 26 Feb 2025 02:28:01 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=10.30.226.201 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1740536881; cv=none; b=QOjyzLEj9CwwfqzD6R8Msa/vwrEbDUkIkIOLd6au8zMGTRYzFjsX77yAq7dCbg0bZKjU2glmtrQfji0AiA/NB39q/k+c9lJyPknITJYs1NREZz4dV5EzzFg9/WrXvfs3NXp518grBOAXcaUXSIlt2oS8cZl5MunT/7p7NAq7lnc= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1740536881; c=relaxed/simple; bh=1cy0piRTR7U1WPArZe6TCVBe2Oa2wGrl3eN1BqYcIww=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version; b=enCgtM4UXHSsOdyBEB30iBapTG5jVcbsGesdKc7wN0SG9HTzDKVXxdvoOJ04PffNtSBuDvtqbzQfXbBiQcHzrjdi1hC1Q4sqO4ZxZU4Kpwxqnu365pB8VurkcZ3sF/AR1nmXxOdl7c3pPzrRPtbe/E4XQyp7jHm1lSpbW9WdWHk= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.b=M6WPBlTw; arc=none smtp.client-ip=10.30.226.201 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.b="M6WPBlTw" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 3A027C4CEDD; Wed, 26 Feb 2025 02:28:01 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=linuxfoundation.org; s=korg; t=1740536881; bh=1cy0piRTR7U1WPArZe6TCVBe2Oa2wGrl3eN1BqYcIww=; h=From:To:Cc:Subject:Date:Reply-to:From; b=M6WPBlTwxnQIHC/e5QtaQMUvtlj5KVbZRj+hwm9NA/B21BLxiPA+Lwasq8a0ThFEW g4B/xca+LeDsrZOoxj1er2e3nLYBzuBDpZ1RcgNqx9Llm62yKTFPWFn5yMzkVa1IyV /B3O8dtu1p28bA68kjSOJqNWMSnsS5B/VbgXnGmw= From: Greg Kroah-Hartman To: linux-cve-announce@vger.kernel.org Cc: Greg Kroah-Hartman Subject: CVE-2022-49720: block: Fix handling of offline queues in blk_mq_alloc_request_hctx() Date: Wed, 26 Feb 2025 03:24:43 +0100 Message-ID: <2025022632-CVE-2022-49720-b0a8@gregkh> X-Mailer: git-send-email 2.48.1 Precedence: bulk X-Mailing-List: linux-cve-announce@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Reply-to: , X-Developer-Signature: v=1; a=openpgp-sha256; l=3040; i=gregkh@linuxfoundation.org; h=from:subject:message-id; bh=1cy0piRTR7U1WPArZe6TCVBe2Oa2wGrl3eN1BqYcIww=; b=owGbwMvMwCRo6H6F97bub03G02pJDOn7ql6cK5ZXbq/5f9Jt+quNElzbJ/WnfGzjNb2cpOMce qaj/rNyRywLgyATg6yYIsuXbTxH91ccUvQytD0NM4eVCWQIAxenAExEPZxhwXm/ksfGS26FXQ99 YDKnaqfg7fentzIsuHRnin5h7KRZHfn2Zu95Q6+3Jc8XBAA= X-Developer-Key: i=gregkh@linuxfoundation.org; a=openpgp; fpr=F4B60CC5BF78C2214A313DCB3147D40DDB2DFB29 Content-Transfer-Encoding: 8bit Description =========== In the Linux kernel, the following vulnerability has been resolved: block: Fix handling of offline queues in blk_mq_alloc_request_hctx() This patch prevents that test nvme/004 triggers the following: UBSAN: array-index-out-of-bounds in block/blk-mq.h:135:9 index 512 is out of range for type 'long unsigned int [512]' Call Trace: show_stack+0x52/0x58 dump_stack_lvl+0x49/0x5e dump_stack+0x10/0x12 ubsan_epilogue+0x9/0x3b __ubsan_handle_out_of_bounds.cold+0x44/0x49 blk_mq_alloc_request_hctx+0x304/0x310 __nvme_submit_sync_cmd+0x70/0x200 [nvme_core] nvmf_connect_io_queue+0x23e/0x2a0 [nvme_fabrics] nvme_loop_connect_io_queues+0x8d/0xb0 [nvme_loop] nvme_loop_create_ctrl+0x58e/0x7d0 [nvme_loop] nvmf_create_ctrl+0x1d7/0x4d0 [nvme_fabrics] nvmf_dev_write+0xae/0x111 [nvme_fabrics] vfs_write+0x144/0x560 ksys_write+0xb7/0x140 __x64_sys_write+0x42/0x50 do_syscall_64+0x35/0x80 entry_SYSCALL_64_after_hwframe+0x44/0xae The Linux kernel CVE team has assigned CVE-2022-49720 to this issue. Affected and fixed versions =========================== Issue introduced in 4.16 with commit 20e4d813931961fe26d26a1e98b3aba6ec00b130 and fixed in 5.10.124 with commit 7fa28a7c3d74933a4fc22d341b60927952f31c19 Issue introduced in 4.16 with commit 20e4d813931961fe26d26a1e98b3aba6ec00b130 and fixed in 5.15.49 with commit b5e65ef044d627effdc2599040b6d204e003f955 Issue introduced in 4.16 with commit 20e4d813931961fe26d26a1e98b3aba6ec00b130 and fixed in 5.18.6 with commit b202a0bd2580ee5b0453772c46d464152fafff73 Issue introduced in 4.16 with commit 20e4d813931961fe26d26a1e98b3aba6ec00b130 and fixed in 5.19 with commit 14dc7a18abbe4176f5626c13c333670da8e06aa1 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-2022-49720 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: block/blk-mq.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/7fa28a7c3d74933a4fc22d341b60927952f31c19 https://git.kernel.org/stable/c/b5e65ef044d627effdc2599040b6d204e003f955 https://git.kernel.org/stable/c/b202a0bd2580ee5b0453772c46d464152fafff73 https://git.kernel.org/stable/c/14dc7a18abbe4176f5626c13c333670da8e06aa1