BUG: unable to handle kernel paging request in mm_update_next_owner

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: f6d5cb9e Linux 4.19.142
git tree: linux-4.19.y
console output: https://syzkaller.appspot.com/x/log.txt?x=1537dfb1900000
kernel config: https://syzkaller.appspot.com/x/.config?x=30067df04d3254aa
dashboard link: https://syzkaller.appspot.com/bug?extid=53186c1e5efc0343c2e5
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+53186c...@syzkaller.appspotmail.com

BUG: unable to handle kernel paging request at fffffffffffffe90
PGD 8c70067 P4D 8c70067 PUD 8c72067 PMD 0
Oops: 0000 [#1] PREEMPT SMP KASAN
CPU: 0 PID: 12206 Comm: syz-executor.0 Not tainted 4.19.142-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
RIP: 0010:mm_update_next_owner+0x444/0x650 kernel/exit.c:453
Code: 70 fa ff ff 49 39 c5 0f 84 df fe ff ff e8 94 e5 2a 00 4c 8d 85 20 04 00 00 4c 89 c0 48 c1 e8 03 80 3c 18 00 0f 85 18 01 00 00 <4c> 8b bd 20 04 00 00 4d 39 e7 75 95 e9 12 fd ff ff e8 66 e5 2a 00
RSP: 0018:ffff88805cc3fd48 EFLAGS: 00010246
RAX: 1fffffffffffffd2 RBX: dffffc0000000000 RCX: ffffffff813ecb4e
RDX: 0000000000000000 RSI: ffffffff813ecbec RDI: ffff888048800840
RBP: fffffffffffffa70 R08: fffffffffffffe90 R09: 0000000000000000
R10: 0000000000000005 R11: 0000000000000000 R12: ffff888049248b40
R13: ffff88800013f1d0 R14: ffff88801db6c500 R15: ffff88803ca1ed80
FS: 0000000000000000(0000) GS:ffff8880ae600000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: fffffffffffffe90 CR3: 0000000096884000 CR4: 00000000001426f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
exit_mm kernel/exit.c:545 [inline]
do_exit+0xaad/0x2b70 kernel/exit.c:874
do_group_exit+0x125/0x310 kernel/exit.c:990
__do_sys_exit_group kernel/exit.c:1001 [inline]
__se_sys_exit_group kernel/exit.c:999 [inline]
__x64_sys_exit_group+0x3a/0x50 kernel/exit.c:999
do_syscall_64+0xf9/0x620 arch/x86/entry/common.c:293
entry_SYSCALL_64_after_hwframe+0x49/0xbe
RIP: 0033:0x45d5b9
Code: 5d b4 fb ff c3 66 2e 0f 1f 84 00 00 00 00 00 66 90 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 0f 83 2b b4 fb ff c3 66 2e 0f 1f 84 00 00 00 00
RSP: 002b:00007ffea3077bc8 EFLAGS: 00000246 ORIG_RAX: 00000000000000e7
RAX: ffffffffffffffda RBX: 000000000000001e RCX: 000000000045d5b9
RDX: 0000000000416f01 RSI: fffffffffffffff7 RDI: 0000000000000000
RBP: 0000000000000000 R08: 0000000000000000 R09: 00007ffea3077c20
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000001
R13: 00007ffea3077c20 R14: 0000000000000000 R15: 00007ffea3077c30
Modules linked in:
CR2: fffffffffffffe90
---[ end trace cd802cf0b5d605ef ]---
RIP: 0010:mm_update_next_owner+0x444/0x650 kernel/exit.c:453
Code: 70 fa ff ff 49 39 c5 0f 84 df fe ff ff e8 94 e5 2a 00 4c 8d 85 20 04 00 00 4c 89 c0 48 c1 e8 03 80 3c 18 00 0f 85 18 01 00 00 <4c> 8b bd 20 04 00 00 4d 39 e7 75 95 e9 12 fd ff ff e8 66 e5 2a 00
RSP: 0018:ffff88805cc3fd48 EFLAGS: 00010246
RAX: 1fffffffffffffd2 RBX: dffffc0000000000 RCX: ffffffff813ecb4e
RDX: 0000000000000000 RSI: ffffffff813ecbec RDI: ffff888048800840
RBP: fffffffffffffa70 R08: fffffffffffffe90 R09: 0000000000000000
R10: 0000000000000005 R11: 0000000000000000 R12: ffff888049248b40
R13: ffff88800013f1d0 R14: ffff88801db6c500 R15: ffff88803ca1ed80
FS: 0000000000000000(0000) GS:ffff8880ae600000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: fffffffffffffe90 CR3: 0000000096884000 CR4: 00000000001426f0
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.