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=1795154332; b=0q48TvDIyW/0gmjOYnm4NZ62tUr5R4CjUbJhzCShWbHTZJLtiB6IyKqV05xFXcvPDEQH dxJ/VBjGDFFWb0O9dzWiyYD3RzzhGqfda9MsJr3kJ5uXi3+sIT0naqegJRJ5vXC4paXUy h73A0gGBH96Q9yR0sCYbHs1yIQRPCY1oQO5mDFj7gdTXLrcFzprvvkzAl5ug2Iz6qpclu kCQbOUN7K1WIC7ps9IReZMH2/WdlON7o3YzP3zpF6C6nmimmXJZj7dlkXG3k2padcuPIr zkhq+x+qB6U7/Am/9wtWHnAKGX0sTcYyfndazFlfdsyTEC1uufIhGsjtgBl/IHO9gUg== ARC-Message-Signature: i=1; d=subspace.kernel.org; s=arc20261015; a=rsa-sha256; c=relaxed/relaxed; t=1795154332; 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=+cIbs6HzNXp4LQxuIKaQafBW2keGS9lNIOv4op5SWuM=; b=y8EuRqXezP1Xeu++txNK6T5BZgEsMOrgebNXU9V7vny4q6BaXcVsBUL5zcwH4deXtR4A EGdGMcb5fsZ4XugHAVnACYtZB/tctArIEuPMvszkqRwF8mLZNYT0thMjX7NzSLYy1L6Ed Kh0C+JBqWJTXsUstH3v29+xsYVa6dOrqxPFFDFkoEBUP3fmSLhziOqBstSWCsj6MSWMM8 RDdyUJ/7Yn4EMUFdd7/+sEtRUdUNKMH8KFJ6nsBctUaCjqO4596TjV9lIfosSGN1ae01h 6jbYq4+qvFJfthvyFmO0JFpnEF3KR9VmuGP7DqN22bu5UsqyDGJdPn1sc3GkBns+TPA== 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="h5sUhzd/"; 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 129D1606A52D for ; Fri, 20 Nov 2026 05:58:51 +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=h5sUhzd/ Received: by smtp.kernel.org (Postfix) with ESMTPSA id 2BC131F000C4; Fri, 20 Nov 2026 05:58:50 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linuxfoundation.org; s=korg; t=1795154331; bh=+cIbs6HzNXp4LQxuIKaQafBW2keGS9lNIOv4op5SWuM=; h=From:To:Cc:Subject:Date:Reply-To; b=h5sUhzd/6B7Igxe3DCQTtsscVqkNUiseMXNTVZE60XrJ0swM8ieuRPAeXqTR2Ul1v eZTdc/o2Igye+6HTaJkaPBles4KfkWIZ8M/eIz3rUpfHu9xAIEbAdYBK3C2Q9kKCSt /XBPlmuDYhNlFUyk7xRGRXl4CxhRoJJ1P6CDBTg0= From: Greg Kroah-Hartman To: linux-cve-announce@vger.kernel.org Cc: Greg Kroah-Hartman Subject: CVE-2026-99705: mm: memory: fix truncation removing mapped folios Date: Fri, 20 Nov 2026 06:51:31 +0100 Message-ID: <2026112004-CVE-2026-99705-e6dc@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=4946; i=gregkh@linuxfoundation.org; h=from:subject:message-id; bh=uPFWno3/qWSnNI8NAfnpucgWGPmBzm5gqbxJd0I+0hc=; b=owGbwMvMwCRo6H6F97bub03G02pJDFn/7/eEfNbnKOCXi9z5ZcUXK+ZG3rqbLl6iJzTPVbOFy d1/Jf+gI5aFQZCJQVZMkeXLNp6j+ysOKXoZ2p6GmcPKBDKEgYtTACYSZ8gwv3SR/YZJazcWb+uX znF1dOndFXPmK8NcgawaXeZfV0UEQtbZ6GW84z/WpzEDAA== 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: memory: fix truncation removing mapped folios Ayush reported an issue that shmem/tmpfs folios are still mapped when truncating them on production: " BUG: Bad page cache in process ... pfn:... page dumped because: still mapped when deleted " I reproduced the issue with Ayush's reproducer [1] with the latest mm-unstable branch, and I got the following crash info. From the dump message, we can see that truncate_inode_folio() is really trying to remove mapped folios, which is incorrect. " [ 189.171977] page: refcount:3 mapcount:1 mapping:00000000fe168ee1 index:0x3880 pfn:0x191647 [ 189.171995] memcg:ffff0000cc073d40 [ 189.171997] aops:shmem_aops ino:3c01 dentry name(?):"memfd:runsc-memory" [ 189.172006] flags: 0x17fffef0002022d(locked|referenced|uptodate|lru| workingset|swapbacked|node=0|zone=2|lastcpupid=0x3ffff) ....... [ 189.172017] page dumped because: VM_BUG_ON_FOLIO(folio_mapped(folio)) [ 189.172026] ------------[ cut here ]------------ [ 189.172027] kernel BUG at mm/filemap.c:155! [ 189.172057] Internal error: Oops - BUG: 00000000f2000800 [#1] SMP ....... [ 189.177721] CPU: 3 UID: 0 PID: 5521 Comm: repro Kdump: loaded Tainted: 7.3.0-rc4+ #277 PREEMPT(lazy) ....... [ 189.183986] Call trace: [ 189.184124] filemap_unaccount_folio+0xf0/0x1e8 (P) [ 189.184391] __filemap_remove_folio+0x34/0x160 [ 189.184633] filemap_remove_folio+0x4c/0xb0 [ 189.184859] truncate_inode_folio+0x34/0x58 [ 189.185087] shmem_undo_range+0x220/0x658 [ 189.185308] shmem_fallocate+0x2f0/0x470 [ 189.185527] vfs_fallocate+0x128/0x328 ...... [ 189.187078] el0t_64_sync+0x184/0x188 " After analysis, I believe the race exists between truncation and MADV_DONTNEED, and shmem's ->map_pages() merely makes the issue easier to reproduce. Since MADV_DONTNEED synchronously releases the pagetable page before calling tlb_flush_rmaps(), this could cause another thread's truncation to skip zap_pte_range() (due to pmd is none) but still observe the folio's mapcount as non-zero. A possible race scenario is as follows: CPU 0 CPU 1 shmem_fallocate madvise_dontneed_single_vma unmap_mapping_range ....... ...... (filemap_map_pages() remap folios) zap_pte_range truncate_inode_folio zap_empty_pte_table(pmd clear) unmap_mapping_folio ...... zap_pmd_range (saw pmd none, skip) filemap_remove_folio BUG_ON(folio_mapped) tlb_flush_rmaps(remove rmaps) To fix this issue, we should move the pmd clear operation (via zap_empty_pte_table()) to after tlb_flush_rmaps() and use sync_with_folio_pmd_zap() to sync with concurrent zapping, so that when we find a pmd_none() while unmapping a folio without holding the PTL, the folio's mappings are guaranteed to have been removed via tlb_flush_rmaps(). Meanwhile move the second pmd_none() check to where it belongs: if splitting zapped the PMD. The Linux kernel CVE team has assigned CVE-2026-99705 to this issue. Affected and fixed versions =========================== Issue introduced in 6.14 with commit 6375e95f381e3dc85065b6f74263a61522736203 and fixed in 6.18.64 with commit 8011e987026b65f59ea6b6082c777807a008b227 Issue introduced in 6.14 with commit 6375e95f381e3dc85065b6f74263a61522736203 and fixed in 7.3.5 with commit b57cfd4da476a4636bf1ed69dee176cc266e5a06 Issue introduced in 6.14 with commit 6375e95f381e3dc85065b6f74263a61522736203 and fixed in 7.4-rc2 with commit 243cf1f67b365668389832463fc31cbb9fec47af 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-99705 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/internal.h mm/memory.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/8011e987026b65f59ea6b6082c777807a008b227 https://git.kernel.org/stable/c/b57cfd4da476a4636bf1ed69dee176cc266e5a06 https://git.kernel.org/stable/c/243cf1f67b365668389832463fc31cbb9fec47af