syzbot


BUG: unable to handle kernel paging request in mm_update_next_owner

Status: auto-closed as invalid on 2021/03/04 20:21
Subsystems: kernel
[Documentation on labels]
Reported-by: syzbot+5597653669c062e8a248@syzkaller.appspotmail.com
First crash: 1428d, last: 1230d
Discussions (1)
Title Replies (including bot) Last reply
BUG: unable to handle kernel paging request in mm_update_next_owner 0 (1) 2020/07/17 15:09
Similar bugs (4)
Kernel Title Repro Cause bisect Fix bisect Count Last Reported Patched Status
linux-4.19 BUG: unable to handle kernel paging request in mm_update_next_owner 21 772d 1299d 0/1 auto-closed as invalid on 2022/06/06 03:00
linux-4.14 general protection fault in mm_update_next_owner (2) 6 1049d 1138d 0/1 auto-closed as invalid on 2021/09/01 20:39
upstream BUG: unable to handle kernel paging request in mm_update_next_owner (2) kernel 1 866d 862d 0/26 auto-closed as invalid on 2022/01/03 02:17
linux-4.14 BUG: unable to handle kernel paging request in mm_update_next_owner 1 1391d 1391d 0/1 auto-closed as invalid on 2020/09/24 23:44

Sample crash report:
BUG: unable to handle page fault for address: fffffffffffffe90
#PF: supervisor read access in kernel mode
#PF: error_code(0x0000) - not-present page
PGD b08f067 P4D b08f067 PUD b091067 PMD 0 
Oops: 0000 [#1] PREEMPT SMP KASAN
CPU: 0 PID: 24964 Comm: syz-executor.2 Not tainted 5.10.0-rc2-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
RIP: 0010:mm_update_next_owner+0x515/0x7a0 kernel/exit.c:390
Code: 48 fa ff ff 49 39 c7 0f 84 eb fe ff ff e8 53 17 2e 00 48 8d 85 48 04 00 00 48 89 c2 48 c1 ea 03 80 3c 1a 00 0f 85 96 01 00 00 <4c> 8b b5 48 04 00 00 4d 39 e6 75 95 49 89 c5 e9 65 fc ff ff e8 22
RSP: 0018:ffffc9000ba67d58 EFLAGS: 00010246
RAX: fffffffffffffe90 RBX: dffffc0000000000 RCX: ffffffff8141f3af
RDX: 1fffffffffffffd2 RSI: ffffffff8141f44d RDI: ffff8880227529a0
RBP: fffffffffffffa48 R08: 0000000000000001 R09: ffffffff8b00a083
R10: 0000000000000000 R11: 0000000000000000 R12: ffff8880751dcd80
R13: ffff888022752240 R14: 0000000000000000 R15: ffff88801fe81410
FS:  0000000000000000(0000) GS:ffff8880b9e00000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: fffffffffffffe90 CR3: 0000000011b2e000 CR4: 00000000001506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000600
Call Trace:
 exit_mm kernel/exit.c:482 [inline]
 do_exit+0xa29/0x2930 kernel/exit.c:793
 do_group_exit+0x125/0x310 kernel/exit.c:903
 __do_sys_exit_group kernel/exit.c:914 [inline]
 __se_sys_exit_group kernel/exit.c:912 [inline]
 __x64_sys_exit_group+0x3a/0x50 kernel/exit.c:912
 do_syscall_64+0x2d/0x70 arch/x86/entry/common.c:46
 entry_SYSCALL_64_after_hwframe+0x44/0xa9
RIP: 0033:0x45deb9
Code: Unable to access opcode bytes at RIP 0x45de8f.
RSP: 002b:00007ffc563f67f8 EFLAGS: 00000246 ORIG_RAX: 00000000000000e7
RAX: ffffffffffffffda RBX: 000000000000001e RCX: 000000000045deb9
RDX: 0000000000417811 RSI: fffffffffffffff7 RDI: 0000000000000000
RBP: 0000000000000000 R08: 0000000000000000 R09: 00007ffc563f6850
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000001
R13: 00007ffc563f6850 R14: 0000000000000000 R15: 00007ffc563f6860
Modules linked in:
CR2: fffffffffffffe90
---[ end trace 15eb12b4ae20fb0b ]---
RIP: 0010:mm_update_next_owner+0x515/0x7a0 kernel/exit.c:390
Code: 48 fa ff ff 49 39 c7 0f 84 eb fe ff ff e8 53 17 2e 00 48 8d 85 48 04 00 00 48 89 c2 48 c1 ea 03 80 3c 1a 00 0f 85 96 01 00 00 <4c> 8b b5 48 04 00 00 4d 39 e6 75 95 49 89 c5 e9 65 fc ff ff e8 22
RSP: 0018:ffffc9000ba67d58 EFLAGS: 00010246
RAX: fffffffffffffe90 RBX: dffffc0000000000 RCX: ffffffff8141f3af
RDX: 1fffffffffffffd2 RSI: ffffffff8141f44d RDI: ffff8880227529a0
RBP: fffffffffffffa48 R08: 0000000000000001 R09: ffffffff8b00a083
R10: 0000000000000000 R11: 0000000000000000 R12: ffff8880751dcd80
R13: ffff888022752240 R14: 0000000000000000 R15: ffff88801fe81410
FS:  0000000000000000(0000) GS:ffff8880b9e00000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: fffffffffffffe90 CR3: 0000000011b2e000 CR4: 00000000001506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000600

Crashes (11):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2020/11/04 20:20 upstream 4ef8451b3326 cba33199 .config console log report info ci-upstream-kasan-gce-selinux-root
2020/08/04 03:27 upstream bcf876870b95 196277c4 .config console log report ci-upstream-kasan-gce-smack-root
2020/07/30 02:43 upstream d3590ebf6f91 233283a1 .config console log report ci-upstream-kasan-gce
2020/07/26 22:24 upstream 04300d66f0a0 51265195 .config console log report ci-upstream-kasan-gce
2020/07/17 15:08 upstream 8882572675c1 9c812472 .config console log report ci-upstream-kasan-gce
2020/07/15 22:12 upstream e9919e11e219 f3bec699 .config console log report ci-upstream-kasan-gce
2020/05/21 10:45 upstream b85051e755b0 c61086ab .config console log report ci-upstream-kasan-gce-root
2020/04/21 06:00 upstream ae83d0b416db 98a9f9e6 .config console log report ci-upstream-kasan-gce
2020/09/21 13:41 upstream ba4f184e126b 9e1fa68e .config console log report info ci-upstream-kasan-gce-386
2020/09/10 17:25 upstream 7fe10096c150 409809d8 .config console log report ci-upstream-kasan-gce-386
2020/05/16 22:22 upstream 3d1c1e5931ce 37bccd4e .config console log report ci-upstream-kasan-gce-386
* Struck through repros no longer work on HEAD.