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=1792758435; b=ZjgAx9gFw0js4Xmab1BRGk3b349HMlZhQBQOGngNqNa6yuZxjvhHMSJbQ9oyOIHLYmXs m9sLmLGnBfKr5ZutWmWI/9sDMwURRRc6jzLOBa/nvHG69ibXuU3lfc1EEvrSGuV8uMtOM yUOdlGRkZQtthm0YgD3TydCC+V3ZRF0aqClyRR0LdPBjfv/aksy90xxQlUFw2LyJnvqf2 PuXXjRg3WRu4SSxSXhj7eG96pR3dCeKUkk5OQcybwl4Wpqx58uYd93YnGUIpo1/m0BdjP 9bbxtgtuIZxGPT6wekyDpxCp71dd5URifFNRksrq4Uscgz3d43VHcZQmMW+d43Jb9hg== ARC-Message-Signature: i=1; d=subspace.kernel.org; s=arc20261015; a=rsa-sha256; c=relaxed/relaxed; t=1792758435; 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=wGTcgci3O1j141lLEbt3RrYzXxPli98hgDHKGFSyu7c=; b=5W/YK+btypADIIprkIanwyldefB0TvEj+7NHlzceJ6o9vkFxo+bXM+r6GWh6Lk/8qlCl KzgfuDsUgJu4kRHs9hvOezlyWhFeOi8xIGxiLbnySdB3Adb33SYte//AVd0sFFxGnYfv/ Jy3lg/SYdczYdSs4UZ/ugDCji9+lQJcUrp/kz8JJaMlejQ71rD5STx2b6KbdK2uOxpBFX pQLZeORO97RfG/LQTbM8huaWh3ZSOyA6YYue0HirbJkq6UVxhh3RjZNEhJs7ZJ7Qz+Y0b 5VgIGJ9rf406VThBBzEu2bNuL6UnEKPgiKW7X58gLIMGdVH7h7RuFY4N9GeJVXFztYA== 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=q5HQ1n8v; 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 10391606A31A for ; Fri, 23 Oct 2026 12:27:14 +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=q5HQ1n8v Received: by smtp.kernel.org (Postfix) with ESMTPSA id E9AB81F01825; Fri, 23 Oct 2026 12:27:11 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linuxfoundation.org; s=korg; t=1792758434; bh=wGTcgci3O1j141lLEbt3RrYzXxPli98hgDHKGFSyu7c=; h=From:To:Cc:Subject:Date:Reply-To; b=q5HQ1n8vZHLj2granQwSkgHdDZJMnwPqNMMZfs53mU0FHag/Iir4K/GT0qbI2lO7b HpCrrstnXnCDj+o2qBPHs66lTd9g+U/nwqsReGxhwA5xdafA3cYP4qSZfAJX5iJ8aG 3jSDLG9P/ejvsvyU+t9gwuww3MGkta8JkJPeRHzI= From: Greg Kroah-Hartman To: linux-cve-announce@vger.kernel.org Cc: Greg Kroah-Hartman Subject: CVE-2026-98960: btrfs: don't stash io_uring encoded data across -EAGAIN Date: Fri, 23 Oct 2026 14:19:22 +0200 Message-ID: <2026102308-CVE-2026-98960-35ff@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=2200; i=gregkh@linuxfoundation.org; h=from:subject:message-id; bh=0f6S2El2t/WaUKySk4SQZDv9NDkzza5ALa8MD6ly8fA=; b=owGbwMvMwCRo6H6F97bub03G02pJDFm3A/asLtvCtaXm/8PVTT3uBj3C2879PzxN2lnirv7xx Q8mr3y+pSOWhUGQiUFWTJHlyzaeo/srDil6GdqehpnDygQyhIGLUwAmMoubYZ6Vifj3vs1b2zXW 9JQGH38ataGk15phfk3HfD6jrPq9syUK1G6/m8nGF6LJDgA= 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: btrfs: don't stash io_uring encoded data across -EAGAIN Returning -EAGAIN while leaving btrfs_uring_encoded_data in the cmd PDU leaks if the request is cancelled or the ring exits before reissue. io_uring does not free driver PDU allocations on cleanup. Write: io_queue_sqe() always issues with IO_URING_F_NONBLOCK first, so return -EAGAIN before allocating and free data on every exit. Read: free on nowait -EAGAIN too; only -EIOCBQUEUED keeps the allocation for btrfs_uring_read_finished(). The Linux kernel CVE team has assigned CVE-2026-98960 to this issue. Affected and fixed versions =========================== Issue introduced in 6.13 with commit 34310c442e175f286b4c06ab5caa4e0b267ea31c and fixed in 7.2.11 with commit 4d9c1e0a7fb2cfb1cc924acafc194d2c15c3e83e Issue introduced in 6.13 with commit 34310c442e175f286b4c06ab5caa4e0b267ea31c and fixed in 7.3 with commit 51562a8cb11628d3a5e105b4c347ec5473e5745f 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-98960 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: fs/btrfs/ioctl.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/4d9c1e0a7fb2cfb1cc924acafc194d2c15c3e83e https://git.kernel.org/stable/c/51562a8cb11628d3a5e105b4c347ec5473e5745f