KASAN: use-after-free Write in skb_release_data (2)

10 views
Skip to first unread message

syzbot

unread,
Feb 14, 2021, 8:48:19 PM2/14/21
to syzkaller...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: 811218ec Linux 4.19.172
git tree: linux-4.19.y
console output: https://syzkaller.appspot.com/x/log.txt?x=175eac60d00000
kernel config: https://syzkaller.appspot.com/x/.config?x=c1cb1d27398c8808
dashboard link: https://syzkaller.appspot.com/bug?extid=90682d1565b1a02e7b37

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+90682d...@syzkaller.appspotmail.com

device veth1_macvtap left promiscuous mode
device veth0_macvtap left promiscuous mode
device veth1_vlan left promiscuous mode
device veth0_vlan left promiscuous mode
==================================================================
BUG: KASAN: use-after-free in atomic_sub_return syzkaller/managers/linux-4-19/kernel/./include/asm-generic/atomic-instrumented.h:305 [inline]
BUG: KASAN: use-after-free in skb_release_data+0x120/0x920 syzkaller/managers/linux-4-19/kernel/net/core/skbuff.c:572
Write of size 4 at addr ffff8880b3624d60 by task syz-executor.2/15101

CPU: 0 PID: 15101 Comm: syz-executor.2 Not tainted 4.19.172-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
Call Trace:
__dump_stack syzkaller/managers/linux-4-19/kernel/lib/dump_stack.c:77 [inline]
dump_stack+0x1fc/0x2ef syzkaller/managers/linux-4-19/kernel/lib/dump_stack.c:118
print_address_description.cold+0x54/0x219 syzkaller/managers/linux-4-19/kernel/mm/kasan/report.c:256
kasan_report_error.cold+0x8a/0x1b9 syzkaller/managers/linux-4-19/kernel/mm/kasan/report.c:354
kasan_report+0x8f/0xa0 syzkaller/managers/linux-4-19/kernel/mm/kasan/report.c:412
atomic_sub_return syzkaller/managers/linux-4-19/kernel/./include/asm-generic/atomic-instrumented.h:305 [inline]
skb_release_data+0x120/0x920 syzkaller/managers/linux-4-19/kernel/net/core/skbuff.c:572
skb_release_all syzkaller/managers/linux-4-19/kernel/net/core/skbuff.c:640 [inline]
__kfree_skb syzkaller/managers/linux-4-19/kernel/net/core/skbuff.c:654 [inline]
kfree_skb+0x11a/0x3d0 syzkaller/managers/linux-4-19/kernel/net/core/skbuff.c:672
hci_dev_do_open+0xaf0/0x1260 syzkaller/managers/linux-4-19/kernel/net/bluetooth/hci_core.c:1509
hci_dev_open+0x130/0x250 syzkaller/managers/linux-4-19/kernel/net/bluetooth/hci_core.c:1575
hci_sock_ioctl+0x57e/0x7d0 syzkaller/managers/linux-4-19/kernel/net/bluetooth/hci_sock.c:1018
sock_do_ioctl+0xcb/0x2d0 syzkaller/managers/linux-4-19/kernel/net/socket.c:950
sock_ioctl+0x2ef/0x5d0 syzkaller/managers/linux-4-19/kernel/net/socket.c:1074
vfs_ioctl syzkaller/managers/linux-4-19/kernel/fs/ioctl.c:46 [inline]
file_ioctl syzkaller/managers/linux-4-19/kernel/fs/ioctl.c:501 [inline]
do_vfs_ioctl+0xcdb/0x12e0 syzkaller/managers/linux-4-19/kernel/fs/ioctl.c:688
ksys_ioctl+0x9b/0xc0 syzkaller/managers/linux-4-19/kernel/fs/ioctl.c:705
__do_sys_ioctl syzkaller/managers/linux-4-19/kernel/fs/ioctl.c:712 [inline]
__se_sys_ioctl syzkaller/managers/linux-4-19/kernel/fs/ioctl.c:710 [inline]
__x64_sys_ioctl+0x6f/0xb0 syzkaller/managers/linux-4-19/kernel/fs/ioctl.c:710
do_syscall_64+0xf9/0x620 syzkaller/managers/linux-4-19/kernel/arch/x86/entry/common.c:293
entry_SYSCALL_64_after_hwframe+0x49/0xbe
RIP: 0033:0x465b57
Code: 3c 1c 48 f7 d8 49 39 c4 72 b8 e8 a4 4d 02 00 85 c0 78 bd 48 83 c4 08 4c 89 e0 5b 41 5c c3 0f 1f 44 00 00 b8 10 00 00 00 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:00007ffd727003f8 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 0000000002c373bc RCX: 0000000000465b57
RDX: 0000000000000002 RSI: 00000000400448c9 RDI: 0000000000000003
RBP: 0000000000000003 R08: 0000000000000000 R09: 00007f0c5a28c700
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000004
R13: 000000000056ca68 R14: 0000000000000000 R15: 0000000000400538

Allocated by task 15101:
__do_kmalloc_node syzkaller/managers/linux-4-19/kernel/mm/slab.c:3689 [inline]
__kmalloc_node_track_caller+0x4c/0x70 syzkaller/managers/linux-4-19/kernel/mm/slab.c:3703
__kmalloc_reserve syzkaller/managers/linux-4-19/kernel/net/core/skbuff.c:137 [inline]
__alloc_skb+0xae/0x560 syzkaller/managers/linux-4-19/kernel/net/core/skbuff.c:205
alloc_skb syzkaller/managers/linux-4-19/kernel/./include/linux/skbuff.h:995 [inline]
bt_skb_alloc syzkaller/managers/linux-4-19/kernel/./include/net/bluetooth/bluetooth.h:339 [inline]
hci_prepare_cmd+0x2a/0x290 syzkaller/managers/linux-4-19/kernel/net/bluetooth/hci_request.c:292
hci_req_add_ev+0xdc/0x220 syzkaller/managers/linux-4-19/kernel/net/bluetooth/hci_request.c:326
bredr_setup syzkaller/managers/linux-4-19/kernel/net/bluetooth/hci_core.c:289 [inline]
hci_init2_req+0x64b/0x8b0 syzkaller/managers/linux-4-19/kernel/net/bluetooth/hci_core.c:422
__hci_req_sync+0x133/0x8a0 syzkaller/managers/linux-4-19/kernel/net/bluetooth/hci_request.c:205
__hci_init syzkaller/managers/linux-4-19/kernel/net/bluetooth/hci_core.c:874 [inline]
hci_dev_do_open+0xe0d/0x1260 syzkaller/managers/linux-4-19/kernel/net/bluetooth/hci_core.c:1463
hci_dev_open+0x130/0x250 syzkaller/managers/linux-4-19/kernel/net/bluetooth/hci_core.c:1575
hci_sock_ioctl+0x57e/0x7d0 syzkaller/managers/linux-4-19/kernel/net/bluetooth/hci_sock.c:1018
sock_do_ioctl+0xcb/0x2d0 syzkaller/managers/linux-4-19/kernel/net/socket.c:950
sock_ioctl+0x2ef/0x5d0 syzkaller/managers/linux-4-19/kernel/net/socket.c:1074
vfs_ioctl syzkaller/managers/linux-4-19/kernel/fs/ioctl.c:46 [inline]
file_ioctl syzkaller/managers/linux-4-19/kernel/fs/ioctl.c:501 [inline]
do_vfs_ioctl+0xcdb/0x12e0 syzkaller/managers/linux-4-19/kernel/fs/ioctl.c:688
ksys_ioctl+0x9b/0xc0 syzkaller/managers/linux-4-19/kernel/fs/ioctl.c:705
__do_sys_ioctl syzkaller/managers/linux-4-19/kernel/fs/ioctl.c:712 [inline]
__se_sys_ioctl syzkaller/managers/linux-4-19/kernel/fs/ioctl.c:710 [inline]
__x64_sys_ioctl+0x6f/0xb0 syzkaller/managers/linux-4-19/kernel/fs/ioctl.c:710
do_syscall_64+0xf9/0x620 syzkaller/managers/linux-4-19/kernel/arch/x86/entry/common.c:293
entry_SYSCALL_64_after_hwframe+0x49/0xbe

Freed by task 1713:
__cache_free syzkaller/managers/linux-4-19/kernel/mm/slab.c:3503 [inline]
kfree+0xcc/0x210 syzkaller/managers/linux-4-19/kernel/mm/slab.c:3822
skb_free_head syzkaller/managers/linux-4-19/kernel/net/core/skbuff.c:563 [inline]
skb_release_data+0x6de/0x920 syzkaller/managers/linux-4-19/kernel/net/core/skbuff.c:583
skb_release_all syzkaller/managers/linux-4-19/kernel/net/core/skbuff.c:640 [inline]
__kfree_skb syzkaller/managers/linux-4-19/kernel/net/core/skbuff.c:654 [inline]
kfree_skb+0x11a/0x3d0 syzkaller/managers/linux-4-19/kernel/net/core/skbuff.c:672
hci_cmd_work+0x182/0x360 syzkaller/managers/linux-4-19/kernel/net/bluetooth/hci_core.c:4393
process_one_work+0x864/0x1570 syzkaller/managers/linux-4-19/kernel/kernel/workqueue.c:2155
worker_thread+0x64c/0x1130 syzkaller/managers/linux-4-19/kernel/kernel/workqueue.c:2298
kthread+0x33f/0x460 syzkaller/managers/linux-4-19/kernel/kernel/kthread.c:259
ret_from_fork+0x24/0x30 syzkaller/managers/linux-4-19/kernel/arch/x86/entry/entry_64.S:415

The buggy address belongs to the object at ffff8880b3624c80
which belongs to the cache kmalloc-512 of size 512
The buggy address is located 224 bytes inside of
512-byte region [ffff8880b3624c80, ffff8880b3624e80)
The buggy address belongs to the page:
page:ffffea0002cd8900 count:1 mapcount:0 mapping:ffff88813bff0940 index:0x0
flags: 0xfff00000000100(slab)
raw: 00fff00000000100 ffffea0002928fc8 ffffea00025cad88 ffff88813bff0940
raw: 0000000000000000 ffff8880b3624000 0000000100000006 0000000000000000
page dumped because: kasan: bad access detected

Memory state around the buggy address:
ffff8880b3624c00: fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc
ffff8880b3624c80: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb
>ffff8880b3624d00: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb
^
ffff8880b3624d80: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb
ffff8880b3624e00: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb
==================================================================


---
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,
Aug 30, 2021, 8:28:21 AM8/30/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