{"id":"CVE-2026-99705","aliases":[],"cve":{"records":[{"id":"CVE-2026-99705","source":"Linux","state":"PUBLISHED","reasons":[],"replacements":[],"disputed":false,"unsupportedWhenAssigned":false,"reserved":"2026-09-25T10:25:14.430Z","published":"2026-11-20T05:50:46.263Z","modified":"2026-11-20T05:50:46.263Z"}],"publishers":[{"name":"Linux","role":"CNA","organizationId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","modified":"2026-11-20T05:50:46.263Z"}],"references":[{"url":"https://git.kernel.org/stable/c/8011e987026b65f59ea6b6082c777807a008b227","tags":[],"source":"Linux"},{"url":"https://git.kernel.org/stable/c/b57cfd4da476a4636bf1ed69dee176cc266e5a06","tags":[],"source":"Linux"},{"url":"https://git.kernel.org/stable/c/243cf1f67b365668389832463fc31cbb9fec47af","tags":[],"source":"Linux"}],"weaknesses":[],"applicability":[{"source":"Linux","statements":[{"nodes":[{"operator":"OR","negate":false,"cpeMatch":[{"vulnerable":true,"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionStartIncluding":"6.14","versionEndExcluding":"6.18.64"},{"vulnerable":true,"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionStartIncluding":"6.14","versionEndExcluding":"7.3.5"},{"vulnerable":true,"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionStartIncluding":"6.14","versionEndExcluding":"7.4-rc2"}]}]}]}],"prioritization":[]},"title":"mm: memory: fix truncation removing mapped folios","titleSource":"Linux","descriptionSource":"Linux","description":"In the Linux kernel, the following vulnerability has been resolved:\n\nmm: memory: fix truncation removing mapped folios\n\nAyush reported an issue that shmem/tmpfs folios are still mapped when\ntruncating them on production:\n\"\nBUG: Bad page cache in process ...  pfn:...\npage dumped because: still mapped when deleted\n\"\n\nI reproduced the issue with Ayush's reproducer [1] with the latest\nmm-unstable branch, and I got the following crash info.  From the dump\nmessage, we can see that truncate_inode_folio() is really trying to remove\nmapped folios, which is incorrect.\n\n\"\n[  189.171977] page: refcount:3 mapcount:1 mapping:00000000fe168ee1\nindex:0x3880 pfn:0x191647\n[  189.171995] memcg:ffff0000cc073d40\n[  189.171997] aops:shmem_aops ino:3c01 dentry name(?):\"memfd:runsc-memory\"\n[  189.172006] flags: 0x17fffef0002022d(locked|referenced|uptodate|lru|\nworkingset|swapbacked|node=0|zone=2|lastcpupid=0x3ffff)\n.......\n[  189.172017] page dumped because: VM_BUG_ON_FOLIO(folio_mapped(folio))\n[  189.172026] ------------[ cut here ]------------\n[  189.172027] kernel BUG at mm/filemap.c:155!\n[  189.172057] Internal error: Oops - BUG: 00000000f2000800 [#1]  SMP\n.......\n[  189.177721] CPU: 3 UID: 0 PID: 5521 Comm: repro Kdump: loaded Tainted:\n7.3.0-rc4+ #277 PREEMPT(lazy)\n.......\n[  189.183986] Call trace:\n[  189.184124]  filemap_unaccount_folio+0xf0/0x1e8 (P)\n[  189.184391]  __filemap_remove_folio+0x34/0x160\n[  189.184633]  filemap_remove_folio+0x4c/0xb0\n[  189.184859]  truncate_inode_folio+0x34/0x58\n[  189.185087]  shmem_undo_range+0x220/0x658\n[  189.185308]  shmem_fallocate+0x2f0/0x470\n[  189.185527]  vfs_fallocate+0x128/0x328\n......\n[  189.187078]  el0t_64_sync+0x184/0x188\n\"\n\nAfter analysis, I believe the race exists between truncation and\nMADV_DONTNEED, and shmem's ->map_pages() merely makes the issue easier to\nreproduce.  Since MADV_DONTNEED synchronously releases the pagetable page\nbefore calling tlb_flush_rmaps(), this could cause another thread's\ntruncation to skip zap_pte_range() (due to pmd is none) but still observe\nthe folio's mapcount as non-zero.  A possible race scenario is as follows:\n\nCPU 0                           CPU 1\nshmem_fallocate                 madvise_dontneed_single_vma\n  unmap_mapping_range            .......\n  ......\n  (filemap_map_pages() remap folios)\n\t\t\t\t  zap_pte_range\n  truncate_inode_folio\t\t    zap_empty_pte_table(pmd clear)\n    unmap_mapping_folio\n    ......\n      zap_pmd_range (saw pmd none, skip)\n\n  filemap_remove_folio\n    BUG_ON(folio_mapped)\n                                    tlb_flush_rmaps(remove rmaps)\n\nTo fix this issue, we should move the pmd clear operation (via\nzap_empty_pte_table()) to after tlb_flush_rmaps() and use\nsync_with_folio_pmd_zap() to sync with concurrent zapping, so that when we\nfind a pmd_none() while unmapping a folio without holding the PTL, the\nfolio's mappings are guaranteed to have been removed via\ntlb_flush_rmaps().\n\nMeanwhile move the second pmd_none() check to where it belongs: if\nsplitting zapped the PMD.","score":null,"severity":"unknown","published":"2026-11-20T05:50:46.263Z","modified":"2026-11-20T05:50:46.263Z","withdrawn":false,"knownExploited":false,"affected":[],"products":[{"vendor":"Linux","name":"Linux","platforms":[],"versions":[{"version":"6375e95f381e3dc85065b6f74263a61522736203","status":"affected","lessThan":"8011e987026b65f59ea6b6082c777807a008b227","versionType":"git"},{"version":"6375e95f381e3dc85065b6f74263a61522736203","status":"affected","lessThan":"b57cfd4da476a4636bf1ed69dee176cc266e5a06","versionType":"git"},{"version":"6375e95f381e3dc85065b6f74263a61522736203","status":"affected","lessThan":"243cf1f67b365668389832463fc31cbb9fec47af","versionType":"git"}],"defaultStatus":"unaffected","cpes":[],"source":"Linux","url":"https://www.cve.org/CVERecord?id=CVE-2026-99705"},{"vendor":"Linux","name":"Linux","platforms":[],"versions":[{"version":"6.14","status":"affected"},{"version":"0","status":"unaffected","lessThan":"6.14","versionType":"semver"},{"version":"6.18.64","status":"unaffected","lessThanOrEqual":"6.18.*","versionType":"semver"},{"version":"7.3.5","status":"unaffected","lessThanOrEqual":"7.3.*","versionType":"semver"},{"version":"7.4-rc2","status":"unaffected","lessThanOrEqual":"*","versionType":"original_commit_for_fix"}],"defaultStatus":"affected","cpes":[],"source":"Linux","url":"https://www.cve.org/CVERecord?id=CVE-2026-99705"}],"remediation":[],"references":["https://git.kernel.org/stable/c/8011e987026b65f59ea6b6082c777807a008b227","https://git.kernel.org/stable/c/b57cfd4da476a4636bf1ed69dee176cc266e5a06","https://git.kernel.org/stable/c/243cf1f67b365668389832463fc31cbb9fec47af"],"sources":[{"name":"CVE","id":"CVE-2026-99705","modified":"2026-11-20T05:50:46.263Z","url":"https://www.cve.org/CVERecord?id=CVE-2026-99705"}],"assessments":[],"sourceAffected":[],"observedAt":"2026-11-20T06:15:06.697Z","kev":{"status":"not-listed","checkedAt":"2026-11-22T12:25:32.613Z"},"coverage":[{"source":"NVD","status":"available","checkedAt":"2026-11-21T10:40:33.760Z","attemptedAt":"2026-11-21T10:40:33.760Z"},{"source":"GHSA","status":"available","checkedAt":"2026-11-21T10:25:33.354Z","attemptedAt":"2026-11-21T10:25:33.354Z"},{"source":"EUVD","status":"available","checkedAt":"2026-11-21T09:40:36.574Z","attemptedAt":"2026-11-21T09:40:36.574Z"},{"source":"EPSS","status":"available","checkedAt":"2026-11-21T09:25:31.659Z","attemptedAt":"2026-11-21T09:25:31.659Z"}],"evidence":[{"source":"FIRST EPSS","id":"CVE-2026-99705","url":"https://www.first.org/epss/","probability":0.00166,"percentile":0.0602,"date":"2026-11-20","checkedAt":"2026-11-21T09:25:31.659Z"},{"source":"ENISA EUVD","id":"EUVD-2026-130998","url":"https://euvd.enisa.europa.eu/vulnerability/EUVD-2026-130998","modified":"Nov 20, 2026, 5:50:46 AM","checkedAt":"2026-11-21T09:40:36.574Z"},{"source":"GitHub Advisory Database","id":"GHSA-vcxf-c337-w2h7","url":"https://github.com/advisories/GHSA-vcxf-c337-w2h7","modified":"2026-11-20T06:32:08Z","checkedAt":"2026-11-21T10:25:33.354Z"},{"source":"NVD","id":"CVE-2026-99705","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-99705","modified":"2026-11-20T06:18:06.423","checkedAt":"2026-11-21T10:40:33.760Z"}],"aiSummary":null}