Description
In the Linux kernel, the following vulnerability has been resolved: mm, swap: fix potential UAF issue for VMA readahead Since commit 78524b05f1a3 ("mm, swap: avoid redundant swap device pinning"), the common helper for allocating and preparing a folio in the swap cache layer no longer tries to get a swap device reference internally, because all callers of __read_swap_cache_async are already holding a swap entry reference. The repeated swap device pinning isn't needed on the same swap device. Caller of VMA readahead is also holding a reference to the target entry's swap device, but VMA readahead walks the page table, so it might encounter swap entries from other devices, and call __read_swap_cache_async on another device without holding a reference to it. So it is possible to cause a UAF when swapoff of device A raced with swapin on device B, and VMA readahead tries to read swap entries from device A. It's not easy to trigger, but in theory, it could cause real issues. Make VMA readahead try to get the device reference first if the swap device is a different one from the target entry.
Product status
78524b05f1a3e16a5d00cc9c6259c41a9d6003ce (git) before a4145be7b56bfa87dce56415c3ad993071462b8a
78524b05f1a3e16a5d00cc9c6259c41a9d6003ce (git) before 1c2a936edd71e133f2806e68324ec81a4eb07588
6.15
Any version before 6.15
6.17.9 (semver)
6.18 (original_commit_for_fix)
References
git.kernel.org/...c/a4145be7b56bfa87dce56415c3ad993071462b8a
git.kernel.org/...c/1c2a936edd71e133f2806e68324ec81a4eb07588
