general protection fault in mm_update_next_owner (2)

6 views
Skip to first unread message

syzbot

unread,
Nov 1, 2022, 12:07:41 PM11/1/22
to syzkaller...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: 3f8a27f9e27b Linux 4.19.211
git tree: linux-4.19.y
console output: https://syzkaller.appspot.com/x/log.txt?x=10ccdc2e880000
kernel config: https://syzkaller.appspot.com/x/.config?x=9b9277b418617afe
dashboard link: https://syzkaller.appspot.com/bug?extid=e677e5cb9ea5fde263fa
compiler: gcc version 10.2.1 20210110 (Debian 10.2.1-6)

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/98c0bdb4abb3/disk-3f8a27f9.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/ea228ff02669/vmlinux-3f8a27f9.xz

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

caif:caif_disconnect_client(): nothing to disconnect
caif:caif_disconnect_client(): nothing to disconnect
kasan: CONFIG_KASAN_INLINE enabled
kasan: GPF could be caused by NULL-ptr deref or user memory access
general protection fault: 0000 [#1] PREEMPT SMP KASAN
CPU: 0 PID: 5856 Comm: syz-executor.3 Not tainted 4.19.211-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/11/2022
RIP: 0010:__read_once_size include/linux/compiler.h:263 [inline]
RIP: 0010:mm_update_next_owner+0x3c6/0x650 kernel/exit.c:452
Code: 48 8d bd 30 03 00 00 48 89 f8 48 c1 e8 03 80 3c 18 00 0f 85 52 02 00 00 48 8b ad 30 03 00 00 4c 8d 6d 10 4c 89 e8 48 c1 e8 03 <80> 3c 18 00 0f 85 29 02 00 00 48 8b 45 10 48 8d a8 70 fa ff ff 49
RSP: 0018:ffff8881f8107d50 EFLAGS: 00010202
RAX: 0000000000000002 RBX: dffffc0000000000 RCX: ffffffff8138bd9e
RDX: 0000000000000000 RSI: ffffffff8138bdac RDI: ffff88800010ea00
RBP: 0000000000000000 R08: ffff888037d4e460 R09: 0000000000000000
R10: 0000000000000005 R11: 0000000000000000 R12: ffff88808ceeeb80
R13: 0000000000000010 R14: ffff888096f82280 R15: ffff888095c5e040
FS: 0000000000000000(0000) GS:ffff8880ba000000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000001b33b23000 CR3: 0000000235edc000 CR4: 00000000003426f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
exit_mm kernel/exit.c:548 [inline]
do_exit+0xae4/0x2be0 kernel/exit.c:857
do_group_exit+0x125/0x310 kernel/exit.c:967
__do_sys_exit_group kernel/exit.c:978 [inline]
__se_sys_exit_group kernel/exit.c:976 [inline]
__x64_sys_exit_group+0x3a/0x50 kernel/exit.c:976
do_syscall_64+0xf9/0x620 arch/x86/entry/common.c:293
entry_SYSCALL_64_after_hwframe+0x49/0xbe
RIP: 0033:0x7f0536a5f5a9
Code: ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 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 73 01 c3 48 c7 c1 b8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007fff142b2608 EFLAGS: 00000246 ORIG_RAX: 00000000000000e7
RAX: ffffffffffffffda RBX: 000000000000001e RCX: 00007f0536a5f5a9
RDX: 00007f0536a1137b RSI: ffffffffffffffb8 RDI: 0000000000000000
RBP: 0000000000000000 R08: 000000007b2586d1 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000001
R13: 0000000000000000 R14: 0000000000000001 R15: 00007fff142b26f0
Modules linked in:
---[ end trace c2040296cc474364 ]---
RIP: 0010:__read_once_size include/linux/compiler.h:263 [inline]
RIP: 0010:mm_update_next_owner+0x3c6/0x650 kernel/exit.c:452
Code: 48 8d bd 30 03 00 00 48 89 f8 48 c1 e8 03 80 3c 18 00 0f 85 52 02 00 00 48 8b ad 30 03 00 00 4c 8d 6d 10 4c 89 e8 48 c1 e8 03 <80> 3c 18 00 0f 85 29 02 00 00 48 8b 45 10 48 8d a8 70 fa ff ff 49
RSP: 0018:ffff8881f8107d50 EFLAGS: 00010202
RAX: 0000000000000002 RBX: dffffc0000000000 RCX: ffffffff8138bd9e
RDX: 0000000000000000 RSI: ffffffff8138bdac RDI: ffff88800010ea00
RBP: 0000000000000000 R08: ffff888037d4e460 R09: 0000000000000000
R10: 0000000000000005 R11: 0000000000000000 R12: ffff88808ceeeb80
R13: 0000000000000010 R14: ffff888096f82280 R15: ffff888095c5e040
FS: 0000000000000000(0000) GS:ffff8880ba000000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000001b33b23000 CR3: 0000000235edc000 CR4: 00000000003426f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
----------------
Code disassembly (best guess):
0: 48 8d bd 30 03 00 00 lea 0x330(%rbp),%rdi
7: 48 89 f8 mov %rdi,%rax
a: 48 c1 e8 03 shr $0x3,%rax
e: 80 3c 18 00 cmpb $0x0,(%rax,%rbx,1)
12: 0f 85 52 02 00 00 jne 0x26a
18: 48 8b ad 30 03 00 00 mov 0x330(%rbp),%rbp
1f: 4c 8d 6d 10 lea 0x10(%rbp),%r13
23: 4c 89 e8 mov %r13,%rax
26: 48 c1 e8 03 shr $0x3,%rax
* 2a: 80 3c 18 00 cmpb $0x0,(%rax,%rbx,1) <-- trapping instruction
2e: 0f 85 29 02 00 00 jne 0x25d
34: 48 8b 45 10 mov 0x10(%rbp),%rax
38: 48 8d a8 70 fa ff ff lea -0x590(%rax),%rbp
3f: 49 rex.WB


---
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

unread,
Mar 1, 2023, 11:07:39 AM3/1/23
to syzkaller...@googlegroups.com
Auto-closing this bug as obsolete.
Crashes did not happen for a while, no reproducer and no activity.
Reply all
Reply to author
Forward
0 new messages