syzbot


BUG: unable to handle kernel paging request in mm_update_next_owner (2)

Status: auto-closed as invalid on 2022/01/03 02:17
Reported-by: syzbot+ab3c487cd60124d4ab17@syzkaller.appspotmail.com
First crash: 280d, last: 280d
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 186d 713d 0/1 auto-closed as invalid on 2022/06/06 03:00
upstream BUG: unable to handle kernel paging request in mm_update_next_owner 11 645d 755d 0/23 auto-closed as invalid on 2021/03/04 20:21
linux-4.14 general protection fault in mm_update_next_owner (2) 6 463d 552d 0/1 auto-closed as invalid on 2021/09/01 20:39
linux-4.14 BUG: unable to handle kernel paging request in mm_update_next_owner 1 805d 805d 0/1 auto-closed as invalid on 2020/09/24 23:44

Sample crash report:
BUG: unable to handle page fault for address: fffffffffffffb6c
#PF: supervisor read access in kernel mode
#PF: error_code(0x0000) - not-present page
PGD b88f067 P4D b88f067 PUD b891067 PMD 0 
Oops: 0000 [#1] PREEMPT SMP KASAN
CPU: 1 PID: 22222 Comm: syz-executor.2 Not tainted 5.15.0-next-20211103-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
RIP: 0010:mm_update_next_owner+0x447/0x7a0 kernel/exit.c:429
Code: 57 31 00 48 8d bd 6c fb ff ff 48 89 f8 48 c1 e8 03 0f b6 14 18 48 89 f8 83 e0 07 83 c0 03 38 d0 7c 08 84 d2 0f 85 b5 02 00 00 <44> 8b b5 6c fb ff ff 31 ff 41 81 e6 00 00 20 00 44 89 f6 e8 01 59
RSP: 0018:ffffc90010157d88 EFLAGS: 00010246
RAX: 0000000000000007 RBX: dffffc0000000000 RCX: 0000000000000000
RDX: 0000000000000000 RSI: ffffffff814673a0 RDI: fffffffffffffb6c
RBP: 0000000000000000 R08: 0000000000000000 R09: ffffffff8b80a083
R10: ffffffff814673df R11: 0000000000000000 R12: ffff8881543a1500
R13: fffffffffffffb40 R14: 0000000000000000 R15: ffff88801a44b610
FS:  0000000000000000(0000) GS:ffff8880b9d00000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: fffffffffffffb6c CR3: 0000000176dfd000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
 <TASK>
 exit_mm kernel/exit.c:506 [inline]
 do_exit+0xb1f/0x2b40 kernel/exit.c:819
 do_group_exit+0x125/0x310 kernel/exit.c:929
 __do_sys_exit_group kernel/exit.c:940 [inline]
 __se_sys_exit_group kernel/exit.c:938 [inline]
 __x64_sys_exit_group+0x3a/0x50 kernel/exit.c:938
 do_syscall_x64 arch/x86/entry/common.c:50 [inline]
 do_syscall_64+0x35/0xb0 arch/x86/entry/common.c:80
 entry_SYSCALL_64_after_hwframe+0x44/0xae
RIP: 0033:0x7f65e4003ae9
Code: Unable to access opcode bytes at RIP 0x7f65e4003abf.
RSP: 002b:00007ffcbd460368 EFLAGS: 00000246 ORIG_RAX: 00000000000000e7
RAX: ffffffffffffffda RBX: 000000000000001e RCX: 00007f65e4003ae9
RDX: 00007f65e3fb672b RSI: ffffffffffffffbc RDI: 0000000000000000
RBP: 0000000000000000 R08: 00007f65e411bbd8 R09: 0000000000000001
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000001
R13: 0000000000000001 R14: 0000000000000001 R15: 00007ffcbd460450
 </TASK>
Modules linked in:
CR2: fffffffffffffb6c
---[ end trace 2ff7c10df90265de ]---
RIP: 0010:mm_update_next_owner+0x447/0x7a0 kernel/exit.c:429
Code: 57 31 00 48 8d bd 6c fb ff ff 48 89 f8 48 c1 e8 03 0f b6 14 18 48 89 f8 83 e0 07 83 c0 03 38 d0 7c 08 84 d2 0f 85 b5 02 00 00 <44> 8b b5 6c fb ff ff 31 ff 41 81 e6 00 00 20 00 44 89 f6 e8 01 59
RSP: 0018:ffffc90010157d88 EFLAGS: 00010246
RAX: 0000000000000007 RBX: dffffc0000000000 RCX: 0000000000000000
RDX: 0000000000000000 RSI: ffffffff814673a0 RDI: fffffffffffffb6c
RBP: 0000000000000000 R08: 0000000000000000 R09: ffffffff8b80a083
R10: ffffffff814673df R11: 0000000000000000 R12: ffff8881543a1500
R13: fffffffffffffb40 R14: 0000000000000000 R15: ffff88801a44b610
FS:  0000000000000000(0000) GS:ffff8880b9d00000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: fffffffffffffb6c CR3: 0000000176dfd000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
----------------
Code disassembly (best guess):
   0:	57                   	push   %rdi
   1:	31 00                	xor    %eax,(%rax)
   3:	48 8d bd 6c fb ff ff 	lea    -0x494(%rbp),%rdi
   a:	48 89 f8             	mov    %rdi,%rax
   d:	48 c1 e8 03          	shr    $0x3,%rax
  11:	0f b6 14 18          	movzbl (%rax,%rbx,1),%edx
  15:	48 89 f8             	mov    %rdi,%rax
  18:	83 e0 07             	and    $0x7,%eax
  1b:	83 c0 03             	add    $0x3,%eax
  1e:	38 d0                	cmp    %dl,%al
  20:	7c 08                	jl     0x2a
  22:	84 d2                	test   %dl,%dl
  24:	0f 85 b5 02 00 00    	jne    0x2df
* 2a:	44 8b b5 6c fb ff ff 	mov    -0x494(%rbp),%r14d <-- trapping instruction
  31:	31 ff                	xor    %edi,%edi
  33:	41 81 e6 00 00 20 00 	and    $0x200000,%r14d
  3a:	44 89 f6             	mov    %r14d,%esi
  3d:	e8                   	.byte 0xe8
  3e:	01                   	.byte 0x1
  3f:	59                   	pop    %rcx

Crashes (1):
Manager Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Title
ci-upstream-linux-next-kasan-gce-root 2021/11/04 02:17 linux-next 8ccbda2840b7 4c1be0be .config log report info BUG: unable to handle kernel paging request in mm_update_next_owner