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 A1219519DE6 for ; Thu, 17 Sep 2026 16:28:48 +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=1789662529; cv=none; b=aZp/hYw+dZM3A2hsQlOQ3sUS7KUFXuN2zn0ZGKJfF56s0/+0DmMGTsCtfr7SBHBX2Ta3KXhlAhmi5ss6Fc5BdC+sLkl4kSWNZIVnroQbwyo7Fxw+7W+ca1ZqPEuF71B/ISfr9K3izxHz+trRv4uUWTbJn1ujE0mkSgmoT6M60Mg= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1789662529; c=relaxed/simple; bh=UpZta18n3+Ota4/r5XBbdWclGv794tmJs6ugVjkNjbw=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version; b=BMyPGtaJUrZHlD+tv+fm6rCjXbRpop32NgrFjn86AEZjmWsXFgnT8M2pgZqje0NyrRBVCq7TB9KmmUrpyQPSnKHozUtTx/dAfBbIhjGRkvBc1IYC8x3buK31s5XsXTyoUh2cE74lvqfWHj6fRCwlTjoN1qrhoC7r6ZenhhcoG+4= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.b=RYazmIVJ; 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="RYazmIVJ" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 02D3A1F000FF; Thu, 17 Sep 2026 16:28:47 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linuxfoundation.org; s=korg; t=1789662528; bh=Who6oXsDKAQi7EXq3hag2IAQYGH7lfpXJZ9g1OxviBc=; h=From:To:Cc:Subject:Date:Reply-To; b=RYazmIVJMLr3JOmoWesk3MABjVkyoSu/tlaBGrDhEKQ3nL4N1PdjdjcW76xWfkgrg U8Q+htAmCGj8311bUxBULhwn8jHgWN1jrxJ8eqdq7FPpRye3m89Ro0IOPcqeCoYYFh vEWoOLk1WK9ycMW+bWGfQkRnCkgVltoOe8T/Eh6Y= From: Greg Kroah-Hartman To: linux-cve-announce@vger.kernel.org Cc: Greg Kroah-Hartman Subject: CVE-2026-90384: iomap: release the folio batch on iomap callback failures Date: Thu, 17 Sep 2026 17:13:34 +0100 Message-ID: <2026091711-CVE-2026-90384-e7f8@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=2838; i=gregkh@linuxfoundation.org; h=from:subject:message-id; bh=0K27g1iasX1rejbHZMa8d/P72jPNsz2Em05YKZrskx8=; b=owGbwMvMwCRo6H6F97bub03G02pJDFlrBJavZCko2ndor47ZjIiSr5HzV2/5EVZ6Tv8G87w11 q9FdwUHdsSyMAgyMciKKbJ82cZzdH/FIUUvQ9vTMHNYmUCGMHBxCsBEhA8zzOGw26YTcFGvP7Sc 88wJ40gvgdN/bzMs6Li/8ovQF1vrVKP/WjME2b8+kW5/DQA= 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: iomap: release the folio batch on iomap callback failures A sashiko review of an unrelated patch points out that the folio batch mechanism used for iomap zero range fails to release the batch in a couple error scenarios. If either calls to ->iomap_end() or ->iomap_begin() fail, the direct return paths bypass the batch cleanup. The ->iomap_end() case is not a practical issue at the moment because there is no user of the mechanism that returns an error from this path. The ->iomap_begin() case is theoretically possible because XFS can invoke the fill helper and error out at various points thereafter. This subtly complicates things because XFS does not transfer iomap_flags to the iomap data structure in the error path. To deal with both of these issues, first make sure to invoke the cleanup helper in the error path for either fs callback. Second, update the helper to clear the flag unconditionally and release the batch so long as it is populated. This more clearly delineates the purpose of the flag to control the I/O path and not necessarily the status of the fbatch, so add a comment around this as well. The Linux kernel CVE team has assigned CVE-2026-90384 to this issue. Affected and fixed versions =========================== Issue introduced in 6.19 with commit 395ed1ef0012e1bb1e4050e84ba0173b3623112a and fixed in 7.2.6 with commit 34470cc3a8e66751030d7b777dd18d9f2acb48e8 Issue introduced in 6.19 with commit 395ed1ef0012e1bb1e4050e84ba0173b3623112a and fixed in 7.3-rc1 with commit 31e3d833d522746a93d135e8b465d16f8ad33453 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-90384 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/iomap/iter.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/34470cc3a8e66751030d7b777dd18d9f2acb48e8 https://git.kernel.org/stable/c/31e3d833d522746a93d135e8b465d16f8ad33453