UNKNOWNCVSS not yet scoredVulnerability

CVE-2026-99733

In the Linux kernel, the following vulnerability has been resolved: mm/truncate: look again if a folio left the mapping invalidate_inode_pages2_range() skips a folio which no longer belongs to the mapping by the time it has got the folio lock, on the assumption that somebody else has removed it from the page cache. But the folio may have been replaced, and then there is a new folio with the same data at that index. For most cases, like folio migration, that is impossible. However, collapse_file() only checks the refcount of the old folios, under the i_pages lock, and relies on their folio locks from there on. That works for users which repeat the lookup when they find folio->mapping changed. The following scenario is, however, possible: CPU0 pwrite(O_DIRECT) CPU1 collapse_file() kiocb_invalidate_pages() read the folio (old data), lock it refcount check the write completes copy to new_folio kiocb_invalidate_post_direct_write() find_get_entries() -> old folio xas_store(new_folio) folio->mapping = NULL folio_unlock(folio) folio_lock() folio->mapping != mapping -> continue In that scenario, the collapsed folio with the data from before the write stays in the page cache after the write has returned. This used to be impossible, as khugepaged only collapsed files that nobody had open for writing. Restart the lookup at that index, like shmem_undo_range() does. The same problem seems to exist in truncate_inode_pages_range() as well when truncate_inode_folio() fails, so handle it there as well, but slightly differently: simply check once more through find_get_entries().

Properties

Last source
FIRST EPSS
Nvd fetched at
2026-11-22T12:30:49.958423+00:00
Epss score
0.00156
Cve id
CVE-2026-99733
First seen by Signal
2026-11-20T07:38:10+00:00
Name
CVE-2026-99733
Retrieved at
2026-11-22T12:32:29+00:00
Published at
2026-11-20T06:18:10.630
Last modified
2026-11-20T06:18:10.630
Epss percentile
0.04757

Related research

Explore deeper with Ninja Signal's threat intelligence graph

CVE-2026-99733 — Ninja Signal Threat Intelligence | Ninja Signal