Description
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.
Product status
fb7d3bc4149395c1ae99029c852eab6c28fc3c88 (git) before b667df39d98a7a24be7c2a40ff0863dac1ad2cd7
fb7d3bc4149395c1ae99029c852eab6c28fc3c88 (git) before c330e65ea59c4805d6ab6757c4ddfe8c63acef31
fb7d3bc4149395c1ae99029c852eab6c28fc3c88 (git) before 615d9bb2ccad42f9e21d837431e401db2e471195
6.14
Any version before 6.14
6.19.14 (semver)
7.0.1 (semver)
7.1-rc1 (original_commit_for_fix)
References
git.kernel.org/...c/b667df39d98a7a24be7c2a40ff0863dac1ad2cd7
git.kernel.org/...c/c330e65ea59c4805d6ab6757c4ddfe8c63acef31
git.kernel.org/...c/615d9bb2ccad42f9e21d837431e401db2e471195