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=1795158163; b=4kJTqSmhijrH5Qc/KmuDvUIuezb92PbZEtEv5cdwm9ia/QtZtU8AwidAZ8YXlpiCTmFR PSlEyS6UYlYwZYIqWd3GS6rbu+l3kfrhcBDoGswLH1wxehGaAPqk41cFuhn/NJbkTbfYw 3Ft8fNbuq4C33sMhon3ruxjxnYF6i97fnB+PlGMtQQOMqNsiihv2PuQpY+SJcwL0EqlET 63lq67/dpOu6SPASuH9J7UNV4DCtSrnYWGEBtxV1otidsJjxQqmoGrNBN7WRTAwH8t5wl JwrWkziVfnfGxLogWjtNlKWFEn8jGBBjlvpJD2Q4r0BJ9LiFYuu65UhNFUyOtPY+0Yg== ARC-Message-Signature: i=1; d=subspace.kernel.org; s=arc20261015; a=rsa-sha256; c=relaxed/relaxed; t=1795158163; 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=VWi/rAktOouHCNVlNBl8NSaqwLOY2y4Sg9wJYPGOTWw=; b=uORZPyzrL0yrcxoA/JSKEZx+pkBGjsGxUfAnszGXtChjNTuMBJu9SJKTGaM25sAsrFm7 22tz+6mRSMghLCKCajdRLVnIkQ8TF2kDhSrH/ycb9E7iX5lgdCfKCjaIi2ihozyhjUXOh Z+HLp+yzEmEDiTrKXeztP7Fkz9r6apUYgmI/nbGCDuZMVHWipD84pEPakclRlUZQyuPQ1 LntxO3bKwc8aKIQKU2plZEBEn1ywBlKczYwtvtyEL1Mc0Nk54SrUWhhh2+itD8Yn9KNVU R+tODJo4echXAvX4cd5WYTl7sl/ro3AIdBJJrr93hahF5k2i7pr7KRgqxFKFxRmXdnA== 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=j0ToTnOt; 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 70566606A325 for ; Fri, 20 Nov 2026 07:02:43 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.a=rsa-sha256 header.s=korg header.b=j0ToTnOt Received: by smtp.kernel.org (Postfix) with ESMTPSA id 738931F000C4; Fri, 20 Nov 2026 07:02:42 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linuxfoundation.org; s=korg; t=1795158163; bh=VWi/rAktOouHCNVlNBl8NSaqwLOY2y4Sg9wJYPGOTWw=; h=From:To:Cc:Subject:Date:Reply-To; b=j0ToTnOtmk47mkfFb0ydDWsqAQuio3YHt7UEEdi2jNJgGuzOO6U7VPaim5w1QA1PS R3YJv6BoxDLlgQQRnxGxW8g0ike9mNeEnMpCibz2LOFJH5dQohjqLiq0XwOYS7hvKf N3YqkFMRpXEOr6gvbQ4FJYEMjhclFPX8RLxcwCtI= From: Greg Kroah-Hartman To: linux-cve-announce@vger.kernel.org Cc: Greg Kroah-Hartman Subject: CVE-2026-99802: io_uring/register: enforce per-task restrictions in io_uring_register_blind() Date: Fri, 20 Nov 2026 08:02:21 +0100 Message-ID: <2026112017-CVE-2026-99802-c852@gregkh> X-Mailer: git-send-email 2.56.1 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=2317; i=gregkh@linuxfoundation.org; h=from:subject:message-id; bh=9WM81s3STYws0Ah4HvDZI6z4AODORTquYbnXVjR0hPM=; b=owGbwMvMwCRo6H6F97bub03G02pJDFn/P1QWX5DzWs9Uyqnc8+FO6X/GNo+YbQlnwn9qBAuuX bZPx5e7I5aFQZCJQVZMkeXLNp6j+ysOKXoZ2p6GmcPKBDKEgYtTACYyxZlhwemFEzTiBWZnZYSk 7ZktcpFdZt+Lbob5yeJK6ofn3pztcPxp1fJX9x8pK0xcDAA= 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/register: enforce per-task restrictions in io_uring_register_blind() When io_uring_register(2) is invoked with fd == -1, it dispatches directly to io_uring_register_blind() without checking current->io_uring_restrict. As a result, a task with per-task register restrictions installed via IORING_REGISTER_RESTRICTIONS can still invoke blind registration opcodes such as IORING_REGISTER_SEND_MSG_RING even when those opcodes are not in the task's allowed register_op bitmap. Check current->io_uring_restrict->register_op in io_uring_register_blind() before dispatching blind registration opcodes. The Linux kernel CVE team has assigned CVE-2026-99802 to this issue. Affected and fixed versions =========================== Issue introduced in 7.0 with commit ed82f35b926b2e505c14b7006473614b8f58b4f4 and fixed in 7.3.2 with commit 681fc755316c4adb37ce481894fb619ff2c477fd Issue introduced in 7.0 with commit ed82f35b926b2e505c14b7006473614b8f58b4f4 and fixed in 7.4-rc1 with commit 4a93427e99a8524f3612f29ec8bc0da5f8435a51 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-99802 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/register.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/681fc755316c4adb37ce481894fb619ff2c477fd https://git.kernel.org/stable/c/4a93427e99a8524f3612f29ec8bc0da5f8435a51