CVE-2026-99733

published 20 Nov 2026 · updated 20 Nov 2026

mm/truncate: look again if a folio left the mapping

5.0MediumEPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 9cf632e139737314afa889ca18122bc3fddb9120, Kernel f17044fee422605d19e07c4c9f5dc2be7abd7086 and Kernel 7.3.5.

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().

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
LinuxKernel=7.2, >=1b6444331bebb4e586dab30b1fa0612ef482bab4 <9cf632e139737314afa889ca18122bc3fddb9120, >=1b6444331bebb4e586dab30b1fa0612ef482bab4 <f17044fee422605d19e07c4c9f5dc2be7abd70869cf632e139737314afa889ca18122bc3fddb9120, f17044fee422605d19e07c4c9f5dc2be7abd7086
linux-kernel: Kernel>=7.2.0 <7.3.57.3.5

Timeline

Every event on this vulnerability

Related

Other vulnerabilities in Kernel, strongest first

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-99733 severity on Zeptric[![CVE-2026-99733](https://zeptric.io/badge/cve/CVE-2026-99733.svg)](https://zeptric.io/cve/CVE-2026-99733)