UNKNOWNCVSS not yet scoredVulnerability

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

Properties

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

Related research

Explore deeper with Ninja Signal's threat intelligence graph

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