In the Linux kernel, the following vulnerability has been resolved: mm/gup: check folio->mapping under folio lock in memfd_pin_folios() memfd_pin_folios() pins folios from the page cache without taking the folio lock. khugepaged or MADV_COLLAPSE can therefore replace a folio after checking its refcount while memfd_pin_folios() still pins the old folio. The caller then receives a folio which is no longer part of the memfd. For udmabuf and iommufd, this can cause data corruption: DMA accesses the detached folio rather than the live memfd contents. DMA reads can return stale data, while DMA writes update the detached copy and are lost from the live memfd. The detached folio remains pinned, so these accesses do not constitute a use-after-free or target another application's memory. For memfd live update, the stale contents can reappear in the memfd after handover. Lock the folio and recheck folio->mapping before pinning it, like other page cache users do. If the folio was removed, retry the folio lookup from the index that was removed.
https://git.kernel.org/stable/c/71555ae8c7572fd99158013ca2e29187c5d2508d
https://git.kernel.org/stable/c/6ac69b444b85d0e511d9bc15f586ebeed49322fa
https://git.kernel.org/stable/c/4480eb27975b91a28bc058a2ca16f466ebd9d7cd
https://git.kernel.org/stable/c/240bc9b873d3522672db13ea93ec73b7f0461912