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

8 views
Skip to first unread message

syzbot

unread,
Jul 4, 2021, 1:11:21 PM7/4/21
to syzkaller...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: 9f84340f Linux 4.19.196
git tree: linux-4.19.y
console output: https://syzkaller.appspot.com/x/log.txt?x=1308c6e2300000
kernel config: https://syzkaller.appspot.com/x/.config?x=abf37bdf4eb59b8e
dashboard link: https://syzkaller.appspot.com/bug?extid=78c4d62beb9b19658a28

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+78c4d6...@syzkaller.appspotmail.com

netlink: 'syz-executor.2': attribute type 1 has an invalid length.
bond14 (uninitialized): Released all slaves
netlink: 'syz-executor.4': attribute type 1 has an invalid length.
netlink: 'syz-executor.3': attribute type 1 has an invalid length.
bond3 (uninitialized): Released all slaves
BUG: unable to handle kernel paging request at ffffffffffffffb0
PGD 9e6e067 P4D 9e6e067 PUD 9e70067 PMD 0
Oops: 0000 [#1] PREEMPT SMP KASAN
CPU: 1 PID: 7443 Comm: syz-executor.4 Not tainted 4.19.196-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
RIP: 0010:vsscanf+0x1dd/0x24c0 lib/vsprintf.c:2932
Code: 89 e9 48 c1 ea 03 4c 89 ac 24 d8 00 00 00 83 e1 07 41 0f b6 04 24 42 0f b6 14 3a 4c 89 eb 38 ca 7f 08 84 d2 0f 85 e6 1b 00 00 <44> 0f b6 75 00 89 c7 88 44 24 08 44 89 f6 e8 90 8b 72 f9 0f b6 44
RSP: 0018:ffff88820d66ec70 EFLAGS: 00010246
RAX: 0000000000000062 RBX: ffff8882351d0181 RCX: 0000000000000000
RDX: 0000000000000000 RSI: ffffffff87eff42a RDI: 0000000000000001
RBP: ffffffffffffffb0 R08: 0000000000000010 R09: 0000000000000000
R10: 0000000000000001 R11: 0000000000000000 R12: ffff8882351d0180
R13: ffff8882351d0181 R14: 0000000000000000 R15: dffffc0000000000
FS: 00007f9ddc79d700(0000) GS:ffff8880ba100000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: ffffffffffffffb0 CR3: 00000002306fa000 CR4: 00000000001426e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
sscanf+0xbb/0xf0 lib/vsprintf.c:3198
__dev_alloc_name net/core/dev.c:1081 [inline]
dev_alloc_name_ns+0x1c4/0x440 net/core/dev.c:1115
dev_get_valid_name+0x67/0xe0 net/core/dev.c:1150
register_netdevice+0x267/0x10f0 net/core/dev.c:8646
bond_newlink drivers/net/bonding/bond_netlink.c:453 [inline]
bond_newlink+0x47/0xa0 drivers/net/bonding/bond_netlink.c:443
rtnl_newlink+0x1030/0x15c0 net/core/rtnetlink.c:3141
rtnetlink_rcv_msg+0x453/0xb80 net/core/rtnetlink.c:4782
netlink_rcv_skb+0x160/0x440 net/netlink/af_netlink.c:2457
netlink_unicast_kernel net/netlink/af_netlink.c:1320 [inline]
netlink_unicast+0x4d5/0x690 net/netlink/af_netlink.c:1346
netlink_sendmsg+0x6bb/0xc40 net/netlink/af_netlink.c:1911
sock_sendmsg_nosec net/socket.c:651 [inline]
sock_sendmsg+0xc3/0x120 net/socket.c:661
___sys_sendmsg+0x7bb/0x8e0 net/socket.c:2225
__sys_sendmsg net/socket.c:2263 [inline]
__do_sys_sendmsg net/socket.c:2272 [inline]
__se_sys_sendmsg net/socket.c:2270 [inline]
__x64_sys_sendmsg+0x132/0x220 net/socket.c:2270
do_syscall_64+0xf9/0x620 arch/x86/entry/common.c:293
entry_SYSCALL_64_after_hwframe+0x49/0xbe
RIP: 0033:0x4665d9
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 bc ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007f9ddc79d188 EFLAGS: 00000246 ORIG_RAX: 000000000000002e
RAX: ffffffffffffffda RBX: 000000000056bf80 RCX: 00000000004665d9
RDX: 0000000000000000 RSI: 0000000020000040 RDI: 0000000000000004
RBP: 00000000004bfcb9 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 000000000056bf80
R13: 00007ffd43c5308f R14: 00007f9ddc79d300 R15: 0000000000022000
Modules linked in:
CR2: ffffffffffffffb0
---[ end trace 6915ec1cf57f4073 ]---
RIP: 0010:vsscanf+0x1dd/0x24c0 lib/vsprintf.c:2932
Code: 89 e9 48 c1 ea 03 4c 89 ac 24 d8 00 00 00 83 e1 07 41 0f b6 04 24 42 0f b6 14 3a 4c 89 eb 38 ca 7f 08 84 d2 0f 85 e6 1b 00 00 <44> 0f b6 75 00 89 c7 88 44 24 08 44 89 f6 e8 90 8b 72 f9 0f b6 44
RSP: 0018:ffff88820d66ec70 EFLAGS: 00010246
RAX: 0000000000000062 RBX: ffff8882351d0181 RCX: 0000000000000000
RDX: 0000000000000000 RSI: ffffffff87eff42a RDI: 0000000000000001
RBP: ffffffffffffffb0 R08: 0000000000000010 R09: 0000000000000000
R10: 0000000000000001 R11: 0000000000000000 R12: ffff8882351d0180
R13: ffff8882351d0181 R14: 0000000000000000 R15: dffffc0000000000
FS: 00007f9ddc79d700(0000) GS:ffff8880ba100000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: ffffffffffffffb0 CR3: 00000002306fa000 CR4: 00000000001426e0
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,
Feb 11, 2022, 5:53:14 PM2/11/22
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