KASAN: use-after-free Write in tipc_subscrb_rcv_cb

10 views
Skip to first unread message

syzbot

unread,
Mar 28, 2020, 8:23:16 AM3/28/20
to syzkaller...@googlegroups.com
Hello,

syzbot found the following crash on:

HEAD commit: 01364dad Linux 4.14.174
git tree: linux-4.14.y
console output: https://syzkaller.appspot.com/x/log.txt?x=1455cacbe00000
kernel config: https://syzkaller.appspot.com/x/.config?x=664dd71881ab2b2d
dashboard link: https://syzkaller.appspot.com/bug?extid=d6703275a1a5163b6aef
compiler: gcc (GCC) 9.0.0 20181231 (experimental)

Unfortunately, I don't have any reproducer for this crash yet.

IMPORTANT: if you fix the bug, please add the following tag to the commit:
Reported-by: syzbot+d67032...@syzkaller.appspotmail.com

==================================================================
BUG: KASAN: use-after-free in __write_once_size include/linux/compiler.h:207 [inline]
BUG: KASAN: use-after-free in set_pending kernel/locking/qspinlock_paravirt.h:89 [inline]
BUG: KASAN: use-after-free in pv_wait_head_or_lock kernel/locking/qspinlock_paravirt.h:410 [inline]
BUG: KASAN: use-after-free in __pv_queued_spin_lock_slowpath+0x6b2/0x950 kernel/locking/qspinlock.c:465
Write of size 1 at addr ffff888098cecd09 by task kworker/u4:1/32271

CPU: 0 PID: 32271 Comm: kworker/u4:1 Not tainted 4.14.174-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
Workqueue: tipc_rcv tipc_recv_work
Call Trace:
__dump_stack lib/dump_stack.c:17 [inline]
dump_stack+0x13e/0x194 lib/dump_stack.c:58
print_address_description.cold+0x7c/0x1e2 mm/kasan/report.c:252
kasan_report_error mm/kasan/report.c:351 [inline]
kasan_report mm/kasan/report.c:409 [inline]
kasan_report.cold+0xa9/0x2ae mm/kasan/report.c:393
__write_once_size include/linux/compiler.h:207 [inline]
set_pending kernel/locking/qspinlock_paravirt.h:89 [inline]
pv_wait_head_or_lock kernel/locking/qspinlock_paravirt.h:410 [inline]
__pv_queued_spin_lock_slowpath+0x6b2/0x950 kernel/locking/qspinlock.c:465
pv_queued_spin_lock_slowpath arch/x86/include/asm/paravirt.h:669 [inline]
queued_spin_lock_slowpath arch/x86/include/asm/qspinlock.h:52 [inline]
queued_spin_lock include/asm-generic/qspinlock.h:90 [inline]
do_raw_spin_lock+0x189/0x230 kernel/locking/spinlock_debug.c:113
spin_lock_bh include/linux/spinlock.h:322 [inline]
tipc_subscrp_subscribe net/tipc/subscr.c:299 [inline]
tipc_subscrb_rcv_cb+0x4d4/0xa50 net/tipc/subscr.c:338
tipc_receive_from_sock+0x26a/0x460 net/tipc/server.c:273
tipc_recv_work+0x79/0xf0 net/tipc/server.c:547
process_one_work+0x813/0x1540 kernel/workqueue.c:2116
worker_thread+0x5d1/0x1070 kernel/workqueue.c:2250
kthread+0x30d/0x420 kernel/kthread.c:232
ret_from_fork+0x24/0x30 arch/x86/entry/entry_64.S:404

Allocated by task 32271:
save_stack+0x32/0xa0 mm/kasan/kasan.c:447
set_track mm/kasan/kasan.c:459 [inline]
kasan_kmalloc mm/kasan/kasan.c:551 [inline]
kasan_kmalloc+0xbf/0xe0 mm/kasan/kasan.c:529
kmem_cache_alloc_trace+0x14d/0x7b0 mm/slab.c:3618
kmalloc include/linux/slab.h:488 [inline]
kzalloc include/linux/slab.h:661 [inline]
tipc_subscrb_create net/tipc/subscr.c:223 [inline]
tipc_subscrb_connect_cb+0x40/0x150 net/tipc/subscr.c:344
tipc_accept_from_sock+0x25b/0x410 net/tipc/server.c:313
tipc_recv_work+0x79/0xf0 net/tipc/server.c:547
process_one_work+0x813/0x1540 kernel/workqueue.c:2116
worker_thread+0x5d1/0x1070 kernel/workqueue.c:2250
kthread+0x30d/0x420 kernel/kthread.c:232
ret_from_fork+0x24/0x30 arch/x86/entry/entry_64.S:404

Freed by task 6132:
save_stack+0x32/0xa0 mm/kasan/kasan.c:447
set_track mm/kasan/kasan.c:459 [inline]
kasan_slab_free+0x75/0xc0 mm/kasan/kasan.c:524
__cache_free mm/slab.c:3496 [inline]
kfree+0xcb/0x260 mm/slab.c:3815
tipc_subscrb_kref_release net/tipc/subscr.c:155 [inline]
kref_put include/linux/kref.h:70 [inline]
tipc_subscrb_put net/tipc/subscr.c:160 [inline]
tipc_subscrb_delete net/tipc/subscr.c:239 [inline]
tipc_subscrb_release_cb+0x2c/0x40 net/tipc/subscr.c:316
tipc_close_conn+0x169/0x210 net/tipc/server.c:203
tipc_send_to_sock net/tipc/server.c:538 [inline]
tipc_send_work+0x434/0x540 net/tipc/server.c:564
process_one_work+0x813/0x1540 kernel/workqueue.c:2116
worker_thread+0x5d1/0x1070 kernel/workqueue.c:2250
kthread+0x30d/0x420 kernel/kthread.c:232
ret_from_fork+0x24/0x30 arch/x86/entry/entry_64.S:404

The buggy address belongs to the object at ffff888098cecd00
which belongs to the cache kmalloc-96 of size 96
The buggy address is located 9 bytes inside of
96-byte region [ffff888098cecd00, ffff888098cecd60)
The buggy address belongs to the page:
page:ffffea0002633b00 count:1 mapcount:0 mapping:ffff888098cec000 index:0xffff888098cec500
flags: 0xfffe0000000100(slab)
raw: 00fffe0000000100 ffff888098cec000 ffff888098cec500 000000010000001f
raw: ffffea000061b760 ffffea0002657a20 ffff88812fe564c0 0000000000000000
page dumped because: kasan: bad access detected

Memory state around the buggy address:
ffff888098cecc00: 00 00 00 00 00 00 00 00 00 fc fc fc fc fc fc fc
ffff888098cecc80: 00 00 00 00 00 00 00 00 00 00 00 00 fc fc fc fc
>ffff888098cecd00: fb fb fb fb fb fb fb fb fb fb fb fb fc fc fc fc
^
ffff888098cecd80: 00 00 00 00 00 00 00 00 00 00 00 00 fc fc fc fc
ffff888098cece00: 00 00 00 00 00 00 00 00 00 00 00 00 fc fc fc fc
==================================================================


---
This bug 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 bug report. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.

syzbot

unread,
Mar 26, 2021, 2:40:14 PM3/26/21
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