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=1795154428; b=VRniOjHu0gsU6zrjdNlz+/rhUzqbwp3RkMeyaNBd9vgKlPMoej6X8exzKXPMngXh9zyp 0cTd7p08jbGzNK1DkjdFeaiKQK8BYSSQFwaVnvOxaCX/4TIN2lbLpmwxmPgvV3d99MOG2 kzcNC3YXMNDAcrcKkvGKvo9vb+nh7u9rwxCO1n9pAheQsTuF6Dj6P+dt4QPj13Uy716XQ 36ur1RoKKqZDdY66/eohuGW61SYfvafBUhCLksrNJxUOGOgtASnZ774NczLHQaod1ZrGc 1cDpnNF5H3ymGPkN5PnwHG2RO4TFn3XTagnaAs+bGL/m7VoIWkRbIct5gDQx9Qj5hkg== ARC-Message-Signature: i=1; d=subspace.kernel.org; s=arc20261015; a=rsa-sha256; c=relaxed/relaxed; t=1795154428; 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=y4RFyHFB+Ot/5o6yRwYwxnHm2/ohpbVZpyeEJfwen2w=; b=5axeJmOpyQhJd24e9fgzSIJRvh3/9/+evrKD/Wld39CYmave+332x2piEAHQWL8Gdzh9 2DlDDoFwDnQ/JJ/Q8QOIzwi8ASkJkRMMS+qoCWXRhEEM/ikmDSB7w0B/xjX20a6lGAh3f dDd6toN2cPtWYN4gJF8Q0IjSuPV0Q4XXxL71OJZYX1SGOQLJaSXHjMTW1+iMrKasvld59 jzo/Fyef5qur1QoB5UmQMUfkR6VUR67iWNQEdzAifzDL9e5vKeG4OuK49TuDwCqarxV9/ PhKc/Ipp6MmC6webFgJzJISSqifc90D7gTmc7uhfVRMw8kqx48r1yZu659bYCDFMe7g== 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="xPu/mJhb"; 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 CDBE5606A51A for ; Fri, 20 Nov 2026 06:00:28 +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=xPu/mJhb Received: by smtp.kernel.org (Postfix) with ESMTPSA id 293E71F000CA; Fri, 20 Nov 2026 06:00:27 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linuxfoundation.org; s=korg; t=1795154428; bh=y4RFyHFB+Ot/5o6yRwYwxnHm2/ohpbVZpyeEJfwen2w=; h=From:To:Cc:Subject:Date:Reply-To; b=xPu/mJhbi/pKV13QeVavEt5Fp2Jd6C4MidgOp0kFhn/0R/H8OY8T18Y74x1GHtU3u l3hiOMdAsRUXpSrLQPl5w4tmzYVXIX/gCXYBFghog3QgW/BDzFC6zDEzCt4b/jpehe KopLzTImdLmRGEltl0Ypu9+rawmMB7mWrZGwIWLk= From: Greg Kroah-Hartman To: linux-cve-announce@vger.kernel.org Cc: Greg Kroah-Hartman Subject: CVE-2026-99740: mm/shmem: stop retrying folios that cannot be split Date: Fri, 20 Nov 2026 06:52:06 +0100 Message-ID: <2026112017-CVE-2026-99740-af4f@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=3157; i=gregkh@linuxfoundation.org; h=from:subject:message-id; bh=4ZO5bJgUSvqmIQAchf5vX104gJkK/JfJCvu0tDhzETE=; b=owGbwMvMwCRo6H6F97bub03G02pJDFn/78/sd0rQf+d+eJ/txxRVnQdHCnuqp5v97vc8rSX64 oWYvLR9RywLgyATg6yYIsuXbTxH91ccUvQytD0NM4eVCWQIAxenAEyk6yfDbNb8vm0aosJxKnEW RUKr8mWsi8qeMizY3lkcFTPzrb5PJc+Rt1Oeml9gEvAAAA== 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: mm/shmem: stop retrying folios that cannot be split A fault or collapse can insert a large folio crossing EOF after shmem_undo_range() has handled the boundary folios. If splitting that folio fails, truncate_inode_partial_folio() retains it when it is dirty. The final scan then repeatedly finds it because it restarts from an unchanged start. Truncation keeps the inode lock and ignores fatal signals while looping. A concurrent unlink() can then block other directory operations while holding the directory lock and waiting for the file's lock. Advance start past the retained folio, whose truncated part has already been zeroed. Do not move start backwards if the failed split has shrunk the folio. Fix generated by an LLM and sent by Chris Mason in private. [ david: split fixes, simplify descriptions, adjust comments ] The Linux kernel CVE team has assigned CVE-2026-99740 to this issue. Affected and fixed versions =========================== Issue introduced in 6.7 with commit 55ac8bbe358bdd2f3c044c12f249fd22d48fe015 and fixed in 6.12.118 with commit dfedff4a9f0abcd985dcdfbd721dcd9374d6ff12 Issue introduced in 6.7 with commit 55ac8bbe358bdd2f3c044c12f249fd22d48fe015 and fixed in 6.18.64 with commit 1360e0f9a188cfede01d0df81119d925bbfff165 Issue introduced in 6.7 with commit 55ac8bbe358bdd2f3c044c12f249fd22d48fe015 and fixed in 7.3.5 with commit b3239a5a37bba078d83cfb864d47a0cc122f17cd Issue introduced in 6.7 with commit 55ac8bbe358bdd2f3c044c12f249fd22d48fe015 and fixed in 7.4-rc2 with commit a842a1f947da8a7020e72f885ffbf2ce6a93685f Issue introduced in 6.1.69 with commit da9b7c651c6517c2de1099136ed87c0c24f864dd Issue introduced in 6.6.8 with commit 7a4ae7acd20805940307be98b304871a43288a01 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-99740 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: mm/shmem.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/dfedff4a9f0abcd985dcdfbd721dcd9374d6ff12 https://git.kernel.org/stable/c/1360e0f9a188cfede01d0df81119d925bbfff165 https://git.kernel.org/stable/c/b3239a5a37bba078d83cfb864d47a0cc122f17cd https://git.kernel.org/stable/c/a842a1f947da8a7020e72f885ffbf2ce6a93685f