Hello,
syzbot found the following issue on:
HEAD commit: 97a8651c Linux 4.19.189
git tree: linux-4.19.y
console output:
https://syzkaller.appspot.com/x/log.txt?x=1794b9d5d00000
kernel config:
https://syzkaller.appspot.com/x/.config?x=82311d18bf81a023
dashboard link:
https://syzkaller.appspot.com/bug?extid=92833989808cfa785fb7
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+928339...@syzkaller.appspotmail.com
R10: 0000000020000080 R11: 0000000000000246 R12: 0000000000000002
R13: 00007ffc49e3e83f R14: 00007f8926493300 R15: 0000000000022000
ieee802154 phy0 wpan0: encryption failed: -22
ieee802154 phy1 wpan1: encryption failed: -22
==================================================================
BUG: KASAN: use-after-free in __read_once_size include/linux/compiler.h:261 [inline]
BUG: KASAN: use-after-free in skb_update_prio net/core/dev.c:3521 [inline]
BUG: KASAN: use-after-free in __dev_queue_xmit+0x2b11/0x2e00 net/core/dev.c:3781
Read of size 8 at addr ffff888030e2dd40 by task aoe_tx0/3132
CPU: 0 PID: 3132 Comm: aoe_tx0 Not tainted 4.19.189-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+0x1fc/0x2ef lib/dump_stack.c:118
print_address_description.cold+0x54/0x219 mm/kasan/report.c:256
kasan_report_error.cold+0x8a/0x1b9 mm/kasan/report.c:354
kasan_report mm/kasan/report.c:412 [inline]
__asan_report_load8_noabort+0x88/0x90 mm/kasan/report.c:433
__read_once_size include/linux/compiler.h:261 [inline]
skb_update_prio net/core/dev.c:3521 [inline]
__dev_queue_xmit+0x2b11/0x2e00 net/core/dev.c:3781
tx+0x68/0xb0 drivers/block/aoe/aoenet.c:63
kthread+0x1d9/0x390 drivers/block/aoe/aoecmd.c:1241
kthread+0x33f/0x460 kernel/kthread.c:259
ret_from_fork+0x24/0x30 arch/x86/entry/entry_64.S:415
Allocated by task 24398:
__do_kmalloc_node mm/slab.c:3689 [inline]
__kmalloc_node+0x4c/0x70 mm/slab.c:3696
kmalloc_node include/linux/slab.h:557 [inline]
kvmalloc_node+0xb4/0xf0 mm/util.c:423
kvmalloc include/linux/mm.h:577 [inline]
kvzalloc include/linux/mm.h:585 [inline]
alloc_netdev_mqs+0x97/0xd50 net/core/dev.c:9144
ieee802154_if_add+0xc3/0x1040 net/mac802154/iface.c:632
ieee802154_add_iface_deprecated+0x3e/0x60 net/mac802154/cfg.c:32
rdev_add_virtual_intf_deprecated net/ieee802154/rdev-ops.h:16 [inline]
ieee802154_add_iface+0x466/0x8f0 net/ieee802154/nl-phy.c:226
genl_family_rcv_msg+0x642/0xc40 net/netlink/genetlink.c:602
genl_rcv_msg+0xbf/0x160 net/netlink/genetlink.c:627
netlink_rcv_skb+0x160/0x440 net/netlink/af_netlink.c:2455
genl_rcv+0x24/0x40 net/netlink/genetlink.c:638
netlink_unicast_kernel net/netlink/af_netlink.c:1318 [inline]
netlink_unicast+0x4d5/0x690 net/netlink/af_netlink.c:1344
netlink_sendmsg+0x6bb/0xc40 net/netlink/af_netlink.c:1909
sock_sendmsg_nosec net/socket.c:622 [inline]
sock_sendmsg+0xc3/0x120 net/socket.c:632
___sys_sendmsg+0x7bb/0x8e0 net/socket.c:2115
__sys_sendmsg net/socket.c:2153 [inline]
__do_sys_sendmsg net/socket.c:2162 [inline]
__se_sys_sendmsg net/socket.c:2160 [inline]
__x64_sys_sendmsg+0x132/0x220 net/socket.c:2160
do_syscall_64+0xf9/0x620 arch/x86/entry/common.c:293
entry_SYSCALL_64_after_hwframe+0x49/0xbe
Freed by task 24398:
__cache_free mm/slab.c:3503 [inline]
kfree+0xcc/0x210 mm/slab.c:3822
kvfree+0x59/0x60 mm/util.c:452
device_release+0x76/0x210 drivers/base/core.c:1076
kobject_cleanup lib/kobject.c:662 [inline]
kobject_release lib/kobject.c:691 [inline]
kref_put include/linux/kref.h:70 [inline]
kobject_put+0x28b/0x5d0 lib/kobject.c:708
netdev_run_todo+0x77f/0xab0 net/core/dev.c:9003
ieee802154_add_iface+0x7cc/0x8f0 net/ieee802154/nl-phy.c:264
genl_family_rcv_msg+0x642/0xc40 net/netlink/genetlink.c:602
genl_rcv_msg+0xbf/0x160 net/netlink/genetlink.c:627
netlink_rcv_skb+0x160/0x440 net/netlink/af_netlink.c:2455
genl_rcv+0x24/0x40 net/netlink/genetlink.c:638
netlink_unicast_kernel net/netlink/af_netlink.c:1318 [inline]
netlink_unicast+0x4d5/0x690 net/netlink/af_netlink.c:1344
netlink_sendmsg+0x6bb/0xc40 net/netlink/af_netlink.c:1909
sock_sendmsg_nosec net/socket.c:622 [inline]
sock_sendmsg+0xc3/0x120 net/socket.c:632
___sys_sendmsg+0x7bb/0x8e0 net/socket.c:2115
__sys_sendmsg net/socket.c:2153 [inline]
__do_sys_sendmsg net/socket.c:2162 [inline]
__se_sys_sendmsg net/socket.c:2160 [inline]
__x64_sys_sendmsg+0x132/0x220 net/socket.c:2160
do_syscall_64+0xf9/0x620 arch/x86/entry/common.c:293
entry_SYSCALL_64_after_hwframe+0x49/0xbe
The buggy address belongs to the object at ffff888030e2d2c0
which belongs to the cache kmalloc-8192 of size 8192
FAULT_INJECTION: forcing a failure.
name failslab, interval 1, probability 0, space 0, times 0
The buggy address is located 2688 bytes inside of
8192-byte region [ffff888030e2d2c0, ffff888030e2f2c0)
The buggy address belongs to the page:
page:ffffea0000c38b00 count:1 mapcount:0 mapping:ffff88813bff2080 index:0x0 compound_mapcount: 0
flags: 0xfff00000008100(slab|head)
raw: 00fff00000008100 ffffea0002cb6408 ffffea0000d2f208 ffff88813bff2080
raw: 0000000000000000 ffff888030e2d2c0 0000000100000001 0000000000000000
page dumped because: kasan: bad access detected
Memory state around the buggy address:
ffff888030e2dc00: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb
ffff888030e2dc80: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb
CPU: 1 PID: 24433 Comm: syz-executor.5 Not tainted 4.19.189-syzkaller #0
>ffff888030e2dd00: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
^
Call Trace:
ffff888030e2dd80: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb
__dump_stack lib/dump_stack.c:77 [inline]
dump_stack+0x1fc/0x2ef lib/dump_stack.c:118
ffff888030e2de00: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb
fail_dump lib/fault-inject.c:51 [inline]
should_fail.cold+0xa/0xf lib/fault-inject.c:149
==================================================================
---
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.