==================================================================
BUG: KCSAN: data-race in lock_vma_under_rcu / vma_prepare

write to 0xffff888136670bf8 of 4 bytes by task 17052 on cpu 1:
 vma_start_write include/linux/mm.h:691 [inline]
 vma_prepare+0x11f/0x520 mm/mmap.c:479
 vma_merge+0x6e5/0xc50 mm/mmap.c:999
 mprotect_fixup+0x2e0/0x650 mm/mprotect.c:631
 do_mprotect_pkey+0x641/0x920 mm/mprotect.c:817
 __do_sys_mprotect mm/mprotect.c:838 [inline]
 __se_sys_mprotect mm/mprotect.c:835 [inline]
 __x64_sys_mprotect+0x48/0x50 mm/mprotect.c:835
 do_syscall_x64 arch/x86/entry/common.c:50 [inline]
 do_syscall_64+0x41/0xc0 arch/x86/entry/common.c:80
 entry_SYSCALL_64_after_hwframe+0x63/0xcd

read to 0xffff888136670bf8 of 4 bytes by task 17054 on cpu 0:
 vma_start_read include/linux/mm.h:645 [inline]
 lock_vma_under_rcu+0xeb/0x2b0 mm/memory.c:5400
 do_user_addr_fault arch/x86/mm/fault.c:1335 [inline]
 handle_page_fault arch/x86/mm/fault.c:1486 [inline]
 exc_page_fault+0x160/0x650 arch/x86/mm/fault.c:1542
 asm_exc_page_fault+0x26/0x30 arch/x86/include/asm/idtentry.h:570

value changed: 0x00000004 -> 0x00000007

Reported by Kernel Concurrency Sanitizer on:
CPU: 0 PID: 17054 Comm: syz-executor.5 Not tainted 6.5.0-rc1-syzkaller-00006-g3f01e9fed845 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/03/2023
==================================================================
loop5: detected capacity change from 0 to 512
EXT4-fs (loop5): mounted filesystem 00000000-0000-0000-0000-000000000000 r/w without journal. Quota mode: writeback.
ext4 filesystem being mounted at /root/syzkaller-testdir2399956199/syzkaller.pHxwFq/119/file0 supports timestamps until 2038-01-19 (0x7fffffff)
EXT4-fs (loop5): unmounting filesystem 00000000-0000-0000-0000-000000000000.