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 21B83387590 for ; Sat, 15 Aug 2026 06:39:28 +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=1786775969; cv=none; b=cw4cGn0FxqapOL6MU7HRmR0PvjvZjm5zUZo8TRKFcgbw2i/rkGCwcMwwzzqSgnTEYBavz8JIf4x0+KaaoTuU0xA9h6eVGo0LoJ20ja1Eq2b5Ab4XOfgAGuV2ENFVl29nLAbo06gsiYNJqG3nvRC5HtvZ9eD/zxT04gFS/pft6LU= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1786775969; c=relaxed/simple; bh=dUofqDYJjx4/3fVOjIbrT6Db11q73yjWEwIrX+ZoJcw=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version; b=N792pnaz/3rH5r71pBnENbYLXN5dB4eNcZ7SX+WuUGN00eiOTNarZAC8jYtPZ9075BmwSOrIEK8Jnm9BrTvrhvBqq7ug9vCqJWTZCYE+HgEp/docJVF5uK+cVmU8AXkGP4qOiSB+4lhcAvEUBva9H9obfvrgqXQXdu16dBOARA8= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.b=FNStw7gc; 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="FNStw7gc" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 770A31F000E9; Sat, 15 Aug 2026 06:39:27 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linuxfoundation.org; s=korg; t=1786775968; bh=GfZM0rG/akjS781VcmGFNReGKLvPn+W10CRicDAYbmU=; h=From:To:Cc:Subject:Date:Reply-To; b=FNStw7gccyCUl/6o7Y1MZLIJvzQf8Fc0CNA/WTKxHmNyE5krC+E9KAAF5iC/UNYjA 26A8GtPw9uow8XMt5UDVP3J7vqAkSP1N4WOQLq1AI3wsc489RjvNvdTJZVi5hWR3Cl U371bJazm/i4SAu41ZQ3Ev4WqpXrsiiuwg8DkDco= From: Greg Kroah-Hartman To: linux-cve-announce@vger.kernel.org Cc: Greg Kroah-Hartman Subject: CVE-2026-74378: RDMA/rxe: Fix TOCTOU heap overflow in get_srq_wqe Date: Sat, 15 Aug 2026 15:11:45 +0900 Message-ID: <2026081504-CVE-2026-74378-ceaf@gregkh> X-Mailer: git-send-email 2.55.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=3147; i=gregkh@linuxfoundation.org; h=from:subject:message-id; bh=z7xojuMvTO8Wgf6k65+KeqdoP2sZOKNs5mgVQPKLWus=; b=owGbwMvMwCRo6H6F97bub03G02pJDFkNjBJPLebKM14KVjxdqe8U0iAYJzPjw/HXBuvtfohW6 39qmHq0I5aFQZCJQVZMkeXLNp6j+ysOKXoZ2p6GmcPKBDKEgYtTACYipM2wYMkcz5fNVluvcGxu ig+TM3TyKnoswDBXnl2iopZtd0OpDvfMVZyHd7PdtFEAAA== 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: RDMA/rxe: Fix TOCTOU heap overflow in get_srq_wqe get_srq_wqe() reads wqe->dma.num_sge from the shared receive queue buffer, which is mapped into userspace. It validates num_sge against max_sge, but then re-reads the same field to calculate the memcpy size. A concurrent userspace thread can modify num_sge between validation and use, causing a heap buffer overflow when copying the WQE into qp->resp.srq_wqe. Read num_sge into a local variable and use it for both the bounds check and the size calculation. The Linux kernel CVE team has assigned CVE-2026-74378 to this issue. Affected and fixed versions =========================== Issue introduced in 4.8 with commit 8700e3e7c4857d28ebaa824509934556da0b3e76 and fixed in 6.1.178 with commit 3cfa2a3adc51b7c57729961a03446962ff10e3d2 Issue introduced in 4.8 with commit 8700e3e7c4857d28ebaa824509934556da0b3e76 and fixed in 6.6.145 with commit cd19a6345e3727adafafa5954b58b13c92e13b80 Issue introduced in 4.8 with commit 8700e3e7c4857d28ebaa824509934556da0b3e76 and fixed in 6.12.97 with commit 3e07ea9579dc9553d2285c26c2823931358aa3b8 Issue introduced in 4.8 with commit 8700e3e7c4857d28ebaa824509934556da0b3e76 and fixed in 6.18.40 with commit 02558c86b6b761063e9399e6b939984500327ef1 Issue introduced in 4.8 with commit 8700e3e7c4857d28ebaa824509934556da0b3e76 and fixed in 7.1.5 with commit b9800d7953d119bcc068c74587d48e4ba0313629 Issue introduced in 4.8 with commit 8700e3e7c4857d28ebaa824509934556da0b3e76 and fixed in 7.2-rc1 with commit 22b8fbded65b8c441b634a185f8da67657df6c50 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-74378 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/infiniband/sw/rxe/rxe_resp.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/3cfa2a3adc51b7c57729961a03446962ff10e3d2 https://git.kernel.org/stable/c/cd19a6345e3727adafafa5954b58b13c92e13b80 https://git.kernel.org/stable/c/3e07ea9579dc9553d2285c26c2823931358aa3b8 https://git.kernel.org/stable/c/02558c86b6b761063e9399e6b939984500327ef1 https://git.kernel.org/stable/c/b9800d7953d119bcc068c74587d48e4ba0313629 https://git.kernel.org/stable/c/22b8fbded65b8c441b634a185f8da67657df6c50