In the Linux kernel, the following vulnerability has been resolved:
mm: call ->free_folio() directly in folio_unmap_invalidate()
We can only call filemap_free_folio() if we have a reference to (or hold a
lock on) the mapping. Otherwise, we've already removed the folio from the
mapping so it no longer pins the mapping and the mapping can be removed,
causing a use-after-free when accessing mapping->a_ops.
Follow the same pattern as __remove_mapping() and load the free_folio
function pointer before dropping the lock on the mapping. That lets us
make filemap_free_folio() static as this was the only caller outside
filemap.c.
References
Configurations
Configuration 1 (hide)
|
History
No history.
Information
Published : 2026-04-24 15:16
Updated : 2026-06-17 10:34
NVD link : CVE-2026-31589
Mitre link : CVE-2026-31589
CVE.ORG link : CVE-2026-31589
JSON object : View
Products Affected
linux
- linux_kernel
CWE
CWE-416
Use After Free
