Description
In the Linux kernel, the following vulnerability has been resolved: mm/mseal: update VMA end correctly on merge Previously we stored the end of the current VMA in curr_end, and then upon iterating to the next VMA updated curr_start to curr_end to advance to the next VMA. However, this doesn't take into account the fact that a VMA might be updated due to a merge by vma_modify_flags(), which can result in curr_end being stale and thus, upon setting curr_start to curr_end, ending up with an incorrect curr_start on the next iteration. Resolve the issue by setting curr_end to vma->vm_end unconditionally to ensure this value remains updated should this occur. While we're here, eliminate this entire class of bug by simply setting const curr_[start/end] to be clamped to the input range and VMAs, which also happens to simplify the logic.
Product status
6c2da14ae1e0a0146587381594559027bd46c059 (git) before 40b3f4700e5535fbe74738cebb9379a40ec66bed
6c2da14ae1e0a0146587381594559027bd46c059 (git) before 83737e34b83a23b2a9bcf586b058b2c2a54c7c6b
6c2da14ae1e0a0146587381594559027bd46c059 (git) before 2697dd8ae721db4f6a53d4f4cbd438212a80f8dc
6.17
Any version before 6.17
6.18.21 (semver)
6.19.11 (semver)
7.0 (original_commit_for_fix)
References
git.kernel.org/...c/40b3f4700e5535fbe74738cebb9379a40ec66bed
git.kernel.org/...c/83737e34b83a23b2a9bcf586b058b2c2a54c7c6b
git.kernel.org/...c/2697dd8ae721db4f6a53d4f4cbd438212a80f8dc