kernel BUG at mm/mmap.c:LINE!

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 13af6c74 Linux 4.19.136
git tree: linux-4.19.y
console output: https://syzkaller.appspot.com/x/log.txt?x=16e8b648900000
kernel config: https://syzkaller.appspot.com/x/.config?x=5b7578d3b5457a49
dashboard link: https://syzkaller.appspot.com/bug?extid=e548418026c799e55635
compiler: gcc (GCC) 10.1.0-syz 20200507

Unfortunately, I don't have any reproducer for this issue yet.

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+e54841...@syzkaller.appspotmail.com

binfmt ffffffff88e6bb80 flags 200cd core_state 0000000000000000
ioctx_table 0000000000000000
owner ffff88804e8fc380 exe_file ffff8880a0b4f580
mmu_notifier_mm 0000000000000000
------------[ cut here ]------------
kernel BUG at mm/mmap.c:393!
invalid opcode: 0000 [#1] PREEMPT SMP KASAN
CPU: 1 PID: 21752 Comm: syz-executor.4 Not tainted 4.19.136-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
RIP: 0010:validate_mm+0x484/0x610 mm/mmap.c:393
Code: a2 a7 d4 ff 44 89 e6 bf ff ff ff ff e8 05 a9 d4 ff 41 83 fc ff 0f 85 9f 07 01 00 e8 86 a7 d4 ff 48 8b 7c 24 18 e8 bc 80 fc ff <0f> 0b e8 75 a7 d4 ff 48 8b 54 24 20 48 b8 00 00 00 00 00 fc ff df
RSP: 0018:ffff8881f10ffbb0 EFLAGS: 00010286
RAX: 0000000000000366 RBX: 0000000000000024 RCX: 0000000000000000
RDX: 0000000000000000 RSI: ffffffff8154cf01 RDI: ffffed103e21ff15
RBP: 0000000000000000 R08: 0000000000000366 R09: 0000000000000000
R10: 0000000000000005 R11: 0000000000000000 R12: 0000000000000001
R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000
FS: 0000000001ef3940(0000) GS:ffff8880ae700000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007ffe812b1bb7 CR3: 00000002014c7000 CR4: 00000000001426e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
mmap_region+0x1012/0x16b0 mm/mmap.c:1780
do_mmap+0x8e8/0x1080 mm/mmap.c:1530
do_mmap_pgoff include/linux/mm.h:2326 [inline]
vm_mmap_pgoff+0x197/0x200 mm/util.c:357
ksys_mmap_pgoff+0x45f/0x5a0 mm/mmap.c:1580
do_syscall_64+0xf9/0x620 arch/x86/entry/common.c:293
entry_SYSCALL_64_after_hwframe+0x49/0xbe
RIP: 0033:0x45ccca
Code: 89 f5 41 54 49 89 fc 55 53 74 35 49 63 e8 48 63 da 4d 89 f9 49 89 e8 4d 63 d6 48 89 da 4c 89 ee 4c 89 e7 b8 09 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 4e 5b 5d 41 5c 41 5d 41 5e 41 5f c3 0f 1f 00
RSP: 002b:00007ffd53c49708 EFLAGS: 00000246 ORIG_RAX: 0000000000000009
RAX: ffffffffffffffda RBX: 0000000000000003 RCX: 000000000045ccca
RDX: 0000000000000003 RSI: 0000000000021000 RDI: 0000000000000000
RBP: ffffffffffffffff R08: ffffffffffffffff R09: 0000000000000000
R10: 0000000000020022 R11: 0000000000000246 R12: 0000000000000000
R13: 0000000000021000 R14: 0000000000020022 R15: 0000000000000000
Modules linked in:
---[ end trace c2ff1347372573b5 ]---
RIP: 0010:validate_mm+0x484/0x610 mm/mmap.c:393
Code: a2 a7 d4 ff 44 89 e6 bf ff ff ff ff e8 05 a9 d4 ff 41 83 fc ff 0f 85 9f 07 01 00 e8 86 a7 d4 ff 48 8b 7c 24 18 e8 bc 80 fc ff <0f> 0b e8 75 a7 d4 ff 48 8b 54 24 20 48 b8 00 00 00 00 00 fc ff df
RSP: 0018:ffff8881f10ffbb0 EFLAGS: 00010286
RAX: 0000000000000366 RBX: 0000000000000024 RCX: 0000000000000000
RDX: 0000000000000000 RSI: ffffffff8154cf01 RDI: ffffed103e21ff15
RBP: 0000000000000000 R08: 0000000000000366 R09: 0000000000000000
R10: 0000000000000005 R11: 0000000000000000 R12: 0000000000000001
R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000
FS: 0000000001ef3940(0000) GS:ffff8880ae700000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007ffe812b1bb7 CR3: 00000002014c7000 CR4: 00000000001426e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400


---
This report is generated by a bot. It may contain errors.
See https://goo.gl/tpsmEJ for more information about syzbot.
syzbot engineers can be reached at syzk...@googlegroups.com.

syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.

[syzbot]

Auto-closing this bug as obsolete.
Crashes did not happen for a while, no reproducer and no activity.