PT-2026-152585
CVE-2026-99705
·
Published
2026-11-20
·
Updated
2026-11-20
Description by
Score
N/A
Not availableNo severity ratings or metrics are available. When they are, we'll update the corresponding info on the page.
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.
Found an issue in the description? Have something to add? Feel free to write us 👾