BUG: unable to handle kernel paging request in do_arpt_get_ctl

4 views
Skip to first unread message

syzbot

unread,
Sep 22, 2020, 12:32:17 AM9/22/20
to syzkaller-upst...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: 10b82d51 Merge branch 'for-5.9-fixes' of git://git.kernel...
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=175646c5900000
kernel config: https://syzkaller.appspot.com/x/.config?x=ffe85b197a57c180
dashboard link: https://syzkaller.appspot.com/bug?extid=10138c69fe218205e9eb
compiler: gcc (GCC) 10.1.0-syz 20200507
CC: [core...@netfilter.org da...@davemloft.net f...@strlen.de kad...@netfilter.org ku...@kernel.org kuz...@ms2.inr.ac.ru linux-...@vger.kernel.org net...@vger.kernel.org netfilt...@vger.kernel.org pa...@netfilter.org yosh...@linux-ipv6.org]

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+10138c...@syzkaller.appspotmail.com

BUG: unable to handle page fault for address: ffff888214d083f0
#PF: supervisor read access in kernel mode
#PF: error_code(0x0000) - not-present page
PGD de01067 P4D de01067 PUD de04067 PMD 109063 PTE 0
Oops: 0000 [#1] PREEMPT SMP KASAN
CPU: 1 PID: 7166 Comm: syz-executor.3 Not tainted 5.9.0-rc5-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
RIP: 0010:arch_atomic64_read arch/x86/include/asm/atomic64_64.h:22 [inline]
RIP: 0010:atomic64_read include/asm-generic/atomic-instrumented.h:838 [inline]
RIP: 0010:atomic_long_read include/asm-generic/atomic-long.h:29 [inline]
RIP: 0010:__mutex_unlock_slowpath+0xad/0x610 kernel/locking/mutex.c:1237
Code: 00 00 00 4c 89 ff e8 62 ee ae f9 4c 89 f8 48 c1 e8 03 80 3c 18 00 0f 85 bb 04 00 00 49 c7 c4 60 b1 1a 8d 48 c7 c5 60 b1 1a 8d <4d> 8b 37 48 b8 00 00 00 00 00 fc ff df 49 c1 ec 03 83 e5 07 49 01
RSP: 0018:ffffc900061c7b48 EFLAGS: 00010246
RAX: 1ffff110429a107e RBX: dffffc0000000000 RCX: ffffffff8807eb9e
RDX: ffffed10429a107f RSI: 0000000000000008 RDI: ffff888214d083f0
RBP: ffffffff8d1ab160 R08: 0000000000000000 R09: ffff888214d083f7
R10: ffffed10429a107e R11: 0000000000000000 R12: ffffffff8d1ab160
R13: 0000000000000000 R14: 1ffff92000c38f6d R15: ffff888214d083f0
FS: 0000000001cee940(0000) GS:ffff8880ae700000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: ffff888214d083f0 CR3: 000000008895e000 CR4: 00000000001526e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
get_entries net/ipv4/netfilter/arp_tables.c:872 [inline]
do_arpt_get_ctl+0x434/0x8f0 net/ipv4/netfilter/arp_tables.c:1450
nf_getsockopt+0x72/0xd0 net/netfilter/nf_sockopt.c:116
ip_getsockopt net/ipv4/ip_sockglue.c:1778 [inline]
ip_getsockopt+0x164/0x1c0 net/ipv4/ip_sockglue.c:1757
tcp_getsockopt+0x86/0xd0 net/ipv4/tcp.c:3876
__sys_getsockopt+0x219/0x4c0 net/socket.c:2173
__do_sys_getsockopt net/socket.c:2188 [inline]
__se_sys_getsockopt net/socket.c:2185 [inline]
__x64_sys_getsockopt+0xba/0x150 net/socket.c:2185
do_syscall_64+0x2d/0x70 arch/x86/entry/common.c:46
entry_SYSCALL_64_after_hwframe+0x44/0xa9
RIP: 0033:0x46010a
Code: b8 34 01 00 00 0f 05 48 3d 01 f0 ff ff 0f 83 3d 89 fb ff c3 66 2e 0f 1f 84 00 00 00 00 00 66 90 49 89 ca b8 37 00 00 00 0f 05 <48> 3d 01 f0 ff ff 0f 83 1a 89 fb ff c3 66 0f 1f 84 00 00 00 00 00
RSP: 002b:000000000169f6f8 EFLAGS: 00000212 ORIG_RAX: 0000000000000037
RAX: ffffffffffffffda RBX: 000000000169f760 RCX: 000000000046010a
RDX: 0000000000000061 RSI: 0000000000000000 RDI: 0000000000000003
RBP: 0000000000000003 R08: 000000000169f70c R09: 000000000000000a
R10: 000000000169f760 R11: 0000000000000212 R12: 0000000000000000
R13: 000000000169fde0 R14: 000000000017bad3 R15: 000000000169fdf0
Modules linked in:
CR2: ffff888214d083f0
---[ end trace a4c8613258562f01 ]---
RIP: 0010:arch_atomic64_read arch/x86/include/asm/atomic64_64.h:22 [inline]
RIP: 0010:atomic64_read include/asm-generic/atomic-instrumented.h:838 [inline]
RIP: 0010:atomic_long_read include/asm-generic/atomic-long.h:29 [inline]
RIP: 0010:__mutex_unlock_slowpath+0xad/0x610 kernel/locking/mutex.c:1237
Code: 00 00 00 4c 89 ff e8 62 ee ae f9 4c 89 f8 48 c1 e8 03 80 3c 18 00 0f 85 bb 04 00 00 49 c7 c4 60 b1 1a 8d 48 c7 c5 60 b1 1a 8d <4d> 8b 37 48 b8 00 00 00 00 00 fc ff df 49 c1 ec 03 83 e5 07 49 01
RSP: 0018:ffffc900061c7b48 EFLAGS: 00010246
RAX: 1ffff110429a107e RBX: dffffc0000000000 RCX: ffffffff8807eb9e
RDX: ffffed10429a107f RSI: 0000000000000008 RDI: ffff888214d083f0
RBP: ffffffff8d1ab160 R08: 0000000000000000 R09: ffff888214d083f7
R10: ffffed10429a107e R11: 0000000000000000 R12: ffffffff8d1ab160
R13: 0000000000000000 R14: 1ffff92000c38f6d R15: ffff888214d083f0
FS: 0000000001cee940(0000) GS:ffff8880ae700000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: ffff888214d083f0 CR3: 000000008895e000 CR4: 00000000001526e0
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

unread,
Dec 16, 2020, 11:25:07 PM12/16/20
to syzkaller-upst...@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