{"id":"AZL-115612","summary":"CVE-2026-99732 affecting package kernel 6.6.161.1-1","details":"In the Linux kernel, the following vulnerability has been resolved:\n\nmm/filemap: read mapping-\u003ea_ops-\u003efree_folio under i_lock\n\nmemory_failure() -\u003e ... -\u003e filemap_remove_folio() can read mapping-\u003ea_ops\nafter the inode has been freed. Once the folio is deleted from the\npagecache it no longer pins the mapping, so after i_lock is dropped\ne.g., a concurrent final iput() can evict and free the inode before\nfilemap_free_folio() looks up mapping-\u003ea_ops-\u003efree_folio.\n\nMost callers hold a reference on the inode, but not all.\n\nDocumentation/filesystems/vfs.rst explicitly states that -\u003efree_folio()\nmust not assume the original address_space mapping still exists.\n\nFix it by loading -\u003efree_folio while i_lock is still held, similar to\nwhat folio_unmap_invalidate() does.\n\nInline filemap_free_folio() into its remaining caller such that\ndelete_from_page_cache_batch() also just loads the callback before\ndropping the i_lock.\n\nThe bug was found by code inspection and has not been reproduced.\n\nFix generated by an LLM and sent by Josef Bacik in private.\n\n[ david: get rid of filemap_free_folio() entirely; improve patch description ]","modified":"2026-11-21T14:17:24.219348273Z","published":"2026-11-20T06:18:10Z","upstream":["CVE-2026-99732"],"references":[{"type":"WEB","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-99732"}],"affected":[{"package":{"name":"kernel","ecosystem":"Azure Linux:3","purl":"pkg:rpm/azure-linux/kernel"},"ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"last_affected":"6.6.161.1-1"}]}],"database_specific":{"source":"https://github.com/microsoft/AzureLinuxVulnerabilityData/blob/main/osv/AZL-115612.json"}}],"schema_version":"1.9.2"}