https://vulnerability.circl.lu Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Tue, 29 Sep 2026 21:31:24 +0000 https://vulnerability.circl.lu/vuln/cve-2026-31589 <p><strong>Affected:</strong> Linux</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>mm: call -&gt;free_folio() directly in folio_unmap_invalidate()</p> <p>We can only call filemap_free_folio() if we have a reference to (or hold a lock on) the mapping. Otherwise, we&#39;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-&gt;a_ops.</p> <p>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.</p> <p><strong>Affected:</strong> Linux</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>mm: call -&gt;free_folio() directly in folio_unmap_invalidate()</p> <p>We can only call filemap_free_folio() if we have a reference to (or hold a lock on) the mapping. Otherwise, we&#39;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-&gt;a_ops.</p> <p>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.</p> https://vulnerability.circl.lu/vuln/cve-2026-31589