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 325C733F5A4 for ; Fri, 8 May 2026 14:22:36 +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=1778250157; cv=none; b=tU6LtwO896ceqRxb+w3I8Kj0SO1w4f+Lx/8R4tB0B+jnuyHuvLmF6/OcG10LugcuqjSjCA0M+6HzC9j+j5ieqIeHFUfhqlzLsFehj2hhc3ZtaK7DAKPyB8KE4N3+5jXlPE9iIYo21SkljCqV22WIctSYVgUhrSzRJZ/XGW27cxc= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1778250157; c=relaxed/simple; bh=vaidfSbRCm8jwUHgQ3na9niloA3R9OsuByJ9fwzX1vU=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version; b=se+VjFCJ0d1QPtKUvVXyix79mF7GZLSbu7xxETS7s5fOtOAdtvFwFf1TDdN+wsbWLcxjxU2BgK+NiUmrh2Nw9kOAIsF8CjkBwKGc7YffkYDm0cM9dOeov8Tnrl9QPbEEQtuXnyhzJ5Y6kQQ36+Op3ZELA0OM4TyyAT+N0sa0raw= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.b=WRCpwAFX; 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="WRCpwAFX" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 72959C2BCB0; Fri, 8 May 2026 14:22:36 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=linuxfoundation.org; s=korg; t=1778250156; bh=vaidfSbRCm8jwUHgQ3na9niloA3R9OsuByJ9fwzX1vU=; h=From:To:Cc:Subject:Date:Reply-To:From; b=WRCpwAFXD9mFX4xNoHJd03EqMdsKAU45RIIQ4oH2iMrtaef3XCqDtUNycPxromzo6 CjPLU9+TYhp9n4Gx77+TLES2NWUL5xzfvjoa+5JXYpSXxpwYLBacWUuPXDvt+1Az6G axz9Y1nWmh0KN1So1Bhi9FKC7z8G+P58ItS2U8nY= From: Greg Kroah-Hartman To: linux-cve-announce@vger.kernel.org Cc: Greg Kroah-Hartman Subject: CVE-2026-43366: io_uring/kbuf: check if target buffer list is still legacy on recycle Date: Fri, 8 May 2026 16:21:35 +0200 Message-ID: <2026050828-CVE-2026-43366-94ff@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=3035; i=gregkh@linuxfoundation.org; h=from:subject:message-id; bh=zGQDrDVEkDBb6QbJAOsD7lwXhL5jpQRYAZfAa43BvL0=; b=owGbwMvMwCRo6H6F97bub03G02pJDJl/P2YsOzFF+HTwgVtTfDZVnDpy/Z4cW2SA6ovc/V/db D7s6qmt6YhlYRBkYpAVU2T5so3n6P6KQ4pehranYeawMoEMYeDiFICJCDYwzHf23/lhqmjsy8J1 i9Zuv2gcuFiKaynD/Or82KTFDx1vCtnJpenoPA0q3Vf5FAA= 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/kbuf: check if target buffer list is still legacy on recycle There's a gap between when the buffer was grabbed and when it potentially gets recycled, where if the list is empty, someone could've upgraded it to a ring provided type. This can happen if the request is forced via io-wq. The legacy recycling is missing checking if the buffer_list still exists, and if it's of the correct type. Add those checks. The Linux kernel CVE team has assigned CVE-2026-43366 to this issue. Affected and fixed versions =========================== Issue introduced in 5.19 with commit c7fb19428d67dd0a2a78a4f237af01d39c78dc5a and fixed in 6.1.167 with commit a7b33671e418fca507feebd1d56e7f4952a4b25c Issue introduced in 5.19 with commit c7fb19428d67dd0a2a78a4f237af01d39c78dc5a and fixed in 6.6.130 with commit 439a6728ec4641ffad1ca796622c19bc525e570f Issue introduced in 5.19 with commit c7fb19428d67dd0a2a78a4f237af01d39c78dc5a and fixed in 6.12.78 with commit f3fb54e7a8b4aadcc2836ee463eec8c88709b8aa Issue introduced in 5.19 with commit c7fb19428d67dd0a2a78a4f237af01d39c78dc5a and fixed in 6.18.19 with commit 50ad880db3013c6fee0ef13781762a39e2e7ef83 Issue introduced in 5.19 with commit c7fb19428d67dd0a2a78a4f237af01d39c78dc5a and fixed in 6.19.9 with commit 97b57f69fee1b61b41acbf37e7720cac9d389fa4 Issue introduced in 5.19 with commit c7fb19428d67dd0a2a78a4f237af01d39c78dc5a and fixed in 7.0 with commit c2c185be5c85d37215397c8e8781abf0a69bec1f 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-43366 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/kbuf.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/a7b33671e418fca507feebd1d56e7f4952a4b25c https://git.kernel.org/stable/c/439a6728ec4641ffad1ca796622c19bc525e570f https://git.kernel.org/stable/c/f3fb54e7a8b4aadcc2836ee463eec8c88709b8aa https://git.kernel.org/stable/c/50ad880db3013c6fee0ef13781762a39e2e7ef83 https://git.kernel.org/stable/c/97b57f69fee1b61b41acbf37e7720cac9d389fa4 https://git.kernel.org/stable/c/c2c185be5c85d37215397c8e8781abf0a69bec1f