| Assigner | Linux |
| Reserved | 2024-02-19 |
| Published | 2024-05-01 |
| Updated | 2024-06-21 |
Description
In the Linux kernel, the following vulnerability has been resolved: fork: defer linking file vma until vma is fully initialized Thorvald reported a WARNING [1]. And the root cause is below race: CPU 1 CPU 2 fork hugetlbfs_fallocate dup_mmap hugetlbfs_punch_hole i_mmap_lock_write(mapping); vma_interval_tree_insert_after -- Child vma is visible through i_mmap tree. i_mmap_unlock_write(mapping); hugetlb_dup_vma_private -- Clear vma_lock outside i_mmap_rwsem! i_mmap_lock_write(mapping); hugetlb_vmdelete_list vma_interval_tree_foreach hugetlb_vma_trylock_write -- Vma_lock is cleared. tmp->vm_ops->open -- Alloc new vma_lock outside i_mmap_rwsem! hugetlb_vma_unlock_write -- Vma_lock is assigned!!! i_mmap_unlock_write(mapping); hugetlb_dup_vma_private() and hugetlb_vm_op_open() are called outside i_mmap_rwsem lock while vma lock can be used in the same time. Fix this by deferring linking file vma until vma is fully initialized. Those vmas should be initialized first before they can be used.
Product status
8d9bfb260814 before 0c42f7e039ab
8d9bfb260814 before 04b0c4191234
8d9bfb260814 before cec11fa2eb51
8d9bfb260814 before dd782da47076
8d9bfb260814 before abdb88dd272b
8d9bfb260814 before 35e351780fa9
6.1
Any version before 6.1
6.1.90
6.1.95
6.6.30
6.6.35
6.8.8
6.9
References
https://git.kernel.org/stable/c/0c42f7e039aba3de6d7dbf92da708e2b2ecba557
https://git.kernel.org/stable/c/04b0c41912349aff11a1bbaef6a722bd7fbb90ac
https://git.kernel.org/stable/c/cec11fa2eb512ebe3a459c185f4aca1d44059bbf
https://git.kernel.org/stable/c/dd782da470761077f4d1120e191f1a35787cda6e
https://git.kernel.org/stable/c/abdb88dd272bbeb93efe01d8e0b7b17e24af3a34
https://git.kernel.org/stable/c/35e351780fa9d8240dd6f7e4f245f9ea37e96c19
