From: syzbot <syzbot+fb2e9e2cc0c13aa477f3@syzkaller.appspotmail.com>
To: davem@davemloft.net, jhs@mojatatu.com, jiri@resnulli.us,
kuba@kernel.org, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org, syzkaller-bugs@googlegroups.com,
xiyou.wangcong@gmail.com
Subject: KASAN: global-out-of-bounds Read in fl_dump_key
Date: Mon, 10 Aug 2020 08:39:25 -0700 [thread overview]
Message-ID: <0000000000006ba6be05ac87c2ff@google.com> (raw)
Hello,
syzbot found the following issue on:
HEAD commit: 7c7ab580 net: Convert to use the fallthrough macro
git tree: net
console output: https://syzkaller.appspot.com/x/log.txt?x=17dab184900000
kernel config: https://syzkaller.appspot.com/x/.config?x=7bb894f55faf8242
dashboard link: https://syzkaller.appspot.com/bug?extid=fb2e9e2cc0c13aa477f3
compiler: gcc (GCC) 10.1.0-syz 20200507
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+fb2e9e2cc0c13aa477f3@syzkaller.appspotmail.com
==================================================================
BUG: KASAN: global-out-of-bounds in fl_dump_key+0x209e/0x22f0 net/sched/cls_flower.c:2781
Read of size 4 at addr ffffffff88deedf4 by task syz-executor.3/14802
CPU: 1 PID: 14802 Comm: syz-executor.3 Not tainted 5.8.0-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
Call Trace:
__dump_stack lib/dump_stack.c:77 [inline]
dump_stack+0x18f/0x20d lib/dump_stack.c:118
print_address_description.constprop.0.cold+0x5/0x436 mm/kasan/report.c:383
__kasan_report mm/kasan/report.c:513 [inline]
kasan_report.cold+0x1f/0x37 mm/kasan/report.c:530
fl_dump_key+0x209e/0x22f0 net/sched/cls_flower.c:2781
fl_tmplt_dump+0xc9/0x250 net/sched/cls_flower.c:3098
tc_chain_fill_node+0x48d/0x7c0 net/sched/cls_api.c:2681
tc_chain_notify+0x187/0x2e0 net/sched/cls_api.c:2707
tc_ctl_chain+0xb30/0x1000 net/sched/cls_api.c:2893
rtnetlink_rcv_msg+0x44e/0xad0 net/core/rtnetlink.c:5563
netlink_rcv_skb+0x15a/0x430 net/netlink/af_netlink.c:2470
netlink_unicast_kernel net/netlink/af_netlink.c:1304 [inline]
netlink_unicast+0x533/0x7d0 net/netlink/af_netlink.c:1330
netlink_sendmsg+0x856/0xd90 net/netlink/af_netlink.c:1919
sock_sendmsg_nosec net/socket.c:651 [inline]
sock_sendmsg+0xcf/0x120 net/socket.c:671
____sys_sendmsg+0x6e8/0x810 net/socket.c:2357
___sys_sendmsg+0xf3/0x170 net/socket.c:2411
__sys_sendmsg+0xe5/0x1b0 net/socket.c:2444
do_syscall_64+0x2d/0x70 arch/x86/entry/common.c:46
entry_SYSCALL_64_after_hwframe+0x44/0xa9
RIP: 0033:0x45ce69
Code: 2d b6 fb ff c3 66 2e 0f 1f 84 00 00 00 00 00 66 90 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 0f 83 fb b5 fb ff c3 66 2e 0f 1f 84 00 00 00 00
RSP: 002b:00007fce49ce7c78 EFLAGS: 00000246 ORIG_RAX: 000000000000002e
RAX: ffffffffffffffda RBX: 000000000002c100 RCX: 000000000045ce69
RDX: 0000000000000000 RSI: 00000000200001c0 RDI: 0000000000000003
RBP: 000000000118c1e0 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 000000000118c1ac
R13: 00007ffc941c811f R14: 00007fce49ce89c0 R15: 000000000118c1ac
The buggy address belongs to the variable:
cooling_device_attr_group+0x354/0x680
Memory state around the buggy address:
ffffffff88deec80: 00 00 03 fa fa fa fa fa 07 fa fa fa fa fa fa fa
ffffffff88deed00: 05 fa fa fa fa fa fa fa 07 fa fa fa fa fa fa fa
>ffffffff88deed80: 06 fa fa fa fa fa fa fa 00 00 fa fa fa fa fa fa
^
ffffffff88deee00: 04 fa fa fa fa fa fa fa 04 fa fa fa fa fa fa fa
ffffffff88deee80: 05 fa fa fa fa fa fa fa 05 fa fa fa fa fa fa fa
==================================================================
---
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 syzkaller@googlegroups.com.
syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.
reply other threads:[~2020-08-10 15:39 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=0000000000006ba6be05ac87c2ff@google.com \
--to=syzbot+fb2e9e2cc0c13aa477f3@syzkaller.appspotmail.com \
--cc=davem@davemloft.net \
--cc=jhs@mojatatu.com \
--cc=jiri@resnulli.us \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=xiyou.wangcong@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).