NetSight
unscored

CVE-2026-99732

In the Linux kernel, the following vulnerability has been resolved: mm/filemap: read mapping->a_ops->free_folio under i_lock memory_failure() -> ...

Impact

In the Linux kernel, the following vulnerability has been resolved: mm/filemap: read mapping->a_ops->free_folio under i_lock memory_failure() -> ... -> filemap_remove_folio() can read mapping->a_ops after the inode has been freed. Once the folio is deleted from the pagecache it no longer pins the mapping, so after i_lock is dropped e.g., a concurrent final iput() can evict and free the inode before filemap_free_folio() looks up mapping->a_ops->free_folio. Most callers hold a reference on the inode, but not all. Documentation/filesystems/vfs.rst explicitly states that ->free_folio() must not assume the original address_space mapping still exists. Fix it by loading ->free_folio while i_lock is still held, similar to what folio_unmap_invalidate() does. Inline filemap_free_folio() into its remaining caller such that delete_from_page_cache_batch() also just loads the callback before dropping the i_lock. The bug was found by code inspection and has not been reproduced. Fix generated by an LLM and sent by Josef Bacik in private. [ david: get rid of filemap_free_folio() entirely; improve patch description ]

Affected products · Linux

ProductAffected versions
Linux
from 59c66c5f8c4fb823240d70553c1686ce4e4dd331 before 842bfdb63ff2f9fcc3edc7ae6a33dfae3747a56e
from 59c66c5f8c4fb823240d70553c1686ce4e4dd331 before dc24e273244e9d712257d5a6c20a32c7f5ca84e6
Versions 4.15, patch: 7.4-rc2, patch: 0, patch: 7.3.5

References