BUG: unable to handle kernel paging request in bpf_fd_array_map_lookup_elem

6 views
Skip to first unread message

syzbot

unread,
Jan 12, 2018, 5:58:05 PM1/12/18
to syzkaller-upst...@googlegroups.com
Hello,

syzkaller hit the following crash on
19d28fbd306e7ae7c1acf05c3e6968b56f0d196b
git://git.kernel.org/pub/scm/linux/kernel/git/davem/net-next.git/master
compiler: gcc (GCC) 7.1.1 20170620
.config is attached
Raw console output is attached.
Unfortunately, I don't have any reproducer for this bug yet.
CC: [a...@kernel.org dan...@iogearbox.net linux-...@vger.kernel.org
net...@vger.kernel.org]

IMPORTANT: if you fix the bug, please add the following tag to the commit:
Reported-by: syzbot+2ed81e...@syzkaller.appspotmail.com
It will help syzbot understand when the bug is fixed. See footer for
details.
If you forward the report, please keep this part and the footer.

netlink: 'syz-executor6': attribute type 25 has an invalid length.
BUG: unable to handle kernel paging request at ffffed004d8fa44f
IP: __read_once_size include/linux/compiler.h:183 [inline]
IP: bpf_fd_array_map_lookup_elem+0x206/0x4c0 kernel/bpf/arraymap.c:374
PGD 21ffee067 P4D 21ffee067 PUD 21ffec067 PMD 0
Oops: 0000 [#1] SMP KASAN
Dumping ftrace buffer:
(ftrace buffer empty)
Modules linked in:
CPU: 0 PID: 13664 Comm: syz-executor2 Not tainted 4.15.0-rc7+ #185
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS
Google 01/01/2011
RIP: 0010:__read_once_size include/linux/compiler.h:183 [inline]
RIP: 0010:bpf_fd_array_map_lookup_elem+0x206/0x4c0 kernel/bpf/arraymap.c:374
RSP: 0018:ffff8801cfa27710 EFLAGS: 00010a02
RAX: dffffc0000000000 RBX: ffff8801cea0d200 RCX: ffffffff8181ec65
RDX: 1ffff1004d8fa44f RSI: ffffc90003abb000 RDI: ffff8801cea0d2c4
RBP: ffff8801cfa277a8 R08: 1ffff10039f44e23 R09: 0000000000000002
R10: ffff8801cfa275e0 R11: 0000000000000000 R12: ffff88026c7d2278
R13: 1ffff10039f44ee4 R14: ffff8801d6d48ec0 R15: ffff8801cfa27780
FS: 00007fb52d2ff700(0000) GS:ffff8801db200000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: ffffed004d8fa44f CR3: 00000001bfc91002 CR4: 00000000001606f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
map_lookup_elem+0x6b5/0xbd0 kernel/bpf/syscall.c:577
SYSC_bpf kernel/bpf/syscall.c:1808 [inline]
SyS_bpf+0x922/0x4400 kernel/bpf/syscall.c:1782
entry_SYSCALL_64_fastpath+0x23/0x9a
RIP: 0033:0x452ac9
RSP: 002b:00007fb52d2fec58 EFLAGS: 00000212 ORIG_RAX: 0000000000000141
RAX: ffffffffffffffda RBX: 000000000071bea0 RCX: 0000000000452ac9
RDX: 0000000000000018 RSI: 0000000020ef0000 RDI: 0000000000000001
RBP: 00000000000003aa R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000212 R12: 00000000006f3890
R13: 00000000ffffffff R14: 00007fb52d2ff6d4 R15: 0000000000000000
Code: 00 44 23 a3 c4 00 00 00 44 0f af e6 49 01 c4 0f 84 8d 01 00 00 e8 db
31 ee ff 4c 89 e2 48 b8 00 00 00 00 00 fc ff df 48 c1 ea 03 <80> 3c 02 00
0f 85 28 02 00 00 49 8b 04 24 4d 8d 67 c0 48 ba 00
RIP: __read_once_size include/linux/compiler.h:183 [inline] RSP:
ffff8801cfa27710
RIP: bpf_fd_array_map_lookup_elem+0x206/0x4c0 kernel/bpf/arraymap.c:374
RSP: ffff8801cfa27710
CR2: ffffed004d8fa44f
---[ end trace 69b76c75d505164b ]---
Kernel panic - not syncing: Fatal exception
Dumping ftrace buffer:
(ftrace buffer empty)
Kernel Offset: disabled
Rebooting in 86400 seconds..


---
This bug is generated by a dumb bot. It may contain errors.
See https://goo.gl/tpsmEJ for details.
Direct all questions to syzk...@googlegroups.com.

syzbot will keep track of this bug report.
If you forgot to add the Reported-by tag, once the fix for this bug is
merged
into any tree, please reply to this email with:
#syz fix: exact-commit-title
To mark this as a duplicate of another syzbot report, please reply with:
#syz dup: exact-subject-of-another-report
If it's a one-off invalid bug report, please reply with:
#syz invalid
Note: if the crash happens again, it will cause creation of a new bug
report.
Note: all commands must start from beginning of the line in the email body.
To upstream this report, please reply with:
#syz upstream
config.txt
raw.log

Dmitry Vyukov

unread,
Jan 13, 2018, 2:17:50 AM1/13/18
to syzbot, 'Dmitry Vyukov' via syzkaller-upstream-moderation
#syz fix:
bpf, array: fix overflow in max_entries and undefined behavior in index_mask
> --
> You received this message because you are subscribed to the Google Groups
> "syzkaller-upstream-moderation" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to syzkaller-upstream-m...@googlegroups.com.
> To post to this group, send email to
> syzkaller-upst...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/syzkaller-upstream-moderation/94eb2c06de3058571b05629c3283%40google.com.
> For more options, visit https://groups.google.com/d/optout.
Reply all
Reply to author
Forward
0 new messages