From mboxrd@z Thu Jan 1 00:00:00 1970 Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.remote-ip=100.103.45.18 ARC-Seal: i=1; d=subspace.kernel.org; s=arc20261015; a=rsa-sha256; cv=none; t=1793706606; b=qo/O4UIJFclo+yt/sB3XJYRdug5f7W5yVnvllEOWJDBaI5nt77V1YaZuTnKiIZjJONtU yZ4mnyTK04TIn8Krfunke2Yi50hRUXr7KiKiCMsCDdcHz0G0rReGlBm35TrNPRyzJnzYY A3M2aBbevh4O6XiFfwQu83n2ZRT1lIIHZq5yWEX8r8t/tXkdhWVKFx6K0TFwO/fP75k9u fz19DQvmZaCbo+7lufyks0ueudQhX/9sgq/FkQEQlcW1eh9Wpy1ax53F7E3MOYcLDYW+m kkehPlHNp1HLP5MgNWg8t4kXqeTqGCHBZAX8vmkAOaLZeq4wOX9DjbDPW9SNd2Y+ZSg== ARC-Message-Signature: i=1; d=subspace.kernel.org; s=arc20261015; a=rsa-sha256; c=relaxed/relaxed; t=1793706606; h=Received:DKIM-Signature:From:To:Cc:Subject:Date:Message-ID:X-Mailer: Reply-To:MIME-Version:Lines:X-Developer-Signature:X-Developer-Key: Content-Transfer-Encoding; bh=lIOOh7hLEmqV4oMyCDUq1RAk5ELt/EACA5rjV8H3Tqo=; b=OIhwvbW4XyLB1SRkZx1K9N7u+vGc5LttMh9URLqRyWUCgJr0YVIPujgNfptQ1JLqa+HP mVk7q10xPYknJ4IZmv0Qk08GX5Tcsr71ruLhnrf4eV6SBHqqfVVoqvrjjq3xhgPE9ujDa i/s3kFOD/UHT0x+r/u3lzpNJNImMl060ZCcK/MtqmbhqsyJ707QQhuNt8P/J9qdApr0qI /8WXZLTyYyvsryq8I0AC9OoYbJa6qrmlIj3AFH99NusX6lLpGzwzH2FP857dc7lpsg9M0 5wrMLSdee1R3y3ePSD+OCyGdjYVaYdtmdC34b6xR6RPTqgwX/6II5YpUYsTOMsXjnRQ== ARC-Authentication-Results: i=1; smtp.subspace.kernel.org; dkim=pass header.d=linuxfoundation.org header.i=@linuxfoundation.org header.a=rsa-sha256 header.s=korg header.b=O6ls594M; arc=none smtp.remote-ip=100.103.45.18 Received: from smtp.kernel.org (quasi.space.kernel.org [100.103.45.18]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (prime256v1)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 82D27606D810 for ; Tue, 3 Nov 2026 11:50:06 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key, unprotected) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.a=rsa-sha256 header.s=korg header.b=O6ls594M Received: by smtp.kernel.org (Postfix) with ESMTPSA id B99151F00A22; Tue, 3 Nov 2026 11:50:05 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linuxfoundation.org; s=korg; t=1793706606; bh=lIOOh7hLEmqV4oMyCDUq1RAk5ELt/EACA5rjV8H3Tqo=; h=From:To:Cc:Subject:Date:Reply-To; b=O6ls594MZUdq/dmvTXd5cJJn4n82kNbDDhrwu+D+YclBNPCosu+ZLL9dTfgbqA0Ta hQiK92Lgy7tCEeNUptB1HNdgJm5PPQBC9xr5v046LI1TSHn221RyDZ+19i366ITF+O D4TXwXoPMpETdG1e1+oinHWkYs5y7Z/7P2W2L7oE= From: Greg Kroah-Hartman To: linux-cve-announce@vger.kernel.org Cc: Greg Kroah-Hartman Subject: CVE-2026-99266: io_uring/zcrx: fix buffer offsets in areas above 4GB Date: Tue, 3 Nov 2026 12:48:26 +0100 Message-ID: <2026110325-CVE-2026-99266-e63b@gregkh> X-Mailer: git-send-email 2.56.0 Reply-To: , X-Mailing-List: linux-cve-announce@vger.kernel.org List-Id: List-Post: List-Help: List-Subscribe: List-Unsubscribe: List-Owner: Precedence: list MIME-Version: 1.0 X-Developer-Signature: v=1; a=openpgp-sha256; l=2347; i=gregkh@linuxfoundation.org; h=from:subject:message-id; bh=pEBMxc3EJR7hVsvFpAj4EVkkw1fGa89tz3P1w6VZnO4=; b=owGbwMvMwCRo6H6F97bub03G02pJDFkvT3GucYxbleTM+sDmzecHH4zvSyn8V2M/2/yQN1k2/ VhjmvjEjlgWBkEmBlkxRZYv23iO7q84pOhlaHsaZg4rE8gQBi5OAZgImzHD/Oqqh4dmnN0SMq+8 f8OO+6LTfBtsfjHM07o6bXveu4QNKQwJZ9JCOj92OAS8AwA= 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: io_uring/zcrx: fix buffer offsets in areas above 4GB io_zcrx_queue_cqe() computes the offset of the buffer in its area from net_iov_idx(), which is an unsigned int, so the shift is done in 32 bits and only the result is widened to the u64 that goes into the CQE. An area can be up to 1TB in size. For every niov beyond the first 4GB the CQE points the application at a buffer 4GB, or a multiple of that, below the one which has the data. It reads the wrong data, and then returns a buffer it doesn't own via the refill queue while the real one is never given back. The Linux kernel CVE team has assigned CVE-2026-99266 to this issue. Affected and fixed versions =========================== Issue introduced in 6.15 with commit 11ed914bbf948c4a37248f2876973ac18014056d and fixed in 6.18.60 with commit 9bfb315e2d0907fbcaf5d0453dd6d873c9aa8d5b Issue introduced in 6.15 with commit 11ed914bbf948c4a37248f2876973ac18014056d and fixed in 7.2.14 with commit 51f4ee29bf0564e6ae7d3540693a9bc1dd2c8fd7 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-99266 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: io_uring/zcrx.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/9bfb315e2d0907fbcaf5d0453dd6d873c9aa8d5b https://git.kernel.org/stable/c/51f4ee29bf0564e6ae7d3540693a9bc1dd2c8fd7 https://git.kernel.org/stable/c/ab4536bf2e5617b04f2d9396f06393c7bbfb071d