KASAN: slab-out-of-bounds Read in hci_le_meta_evt
36 views
Skip to first unread message
syzbot
Jul 31, 2020, 5:56:16 AM7/31/20
to syzkaller...@googlegroups.com
Hello,
syzbot found the following issue on:
HEAD commit: 205a42ce Linux 4.19.135
git tree: linux-4.19.y
console output: https://syzkaller.appspot.com/x/log.txt?x=13c87b60900000
kernel config: https://syzkaller.appspot.com/x/.config?x=155b0b328eb5e700
dashboard link: https://syzkaller.appspot.com/bug?extid=fbbeeb520a74f5c346d1
compiler: gcc (GCC) 10.1.0-syz 20200507
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1502f69b100000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=13379f12900000
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+fbbeeb...@syzkaller.appspotmail.com
IPVS: ftp: loaded support on port[0] = 21
Bluetooth: Unknown advertising packet type: 0xffff
Bluetooth: hci0: advertising data len corrected
Bluetooth: hci0: advertising data len corrected
==================================================================
BUG: KASAN: slab-out-of-bounds in hci_le_ext_adv_report_evt net/bluetooth/hci_event.c:5403 [inline]
BUG: KASAN: slab-out-of-bounds in hci_le_meta_evt+0x345b/0x39c0 net/bluetooth/hci_event.c:5645
Read of size 1 at addr ffff8880a8741a15 by task kworker/u5:2/6466
CPU: 0 PID: 6466 Comm: kworker/u5:2 Not tainted 4.19.135-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
Workqueue: hci0 hci_rx_work
Call Trace:
__dump_stack lib/dump_stack.c:77 [inline]
dump_stack+0x1fc/0x2fe lib/dump_stack.c:118
print_address_description.cold+0x54/0x219 mm/kasan/report.c:256
kasan_report_error.cold+0x8a/0x1c7 mm/kasan/report.c:354
kasan_report mm/kasan/report.c:412 [inline]
__asan_report_load1_noabort+0x88/0x90 mm/kasan/report.c:430
hci_le_ext_adv_report_evt net/bluetooth/hci_event.c:5403 [inline]
hci_le_meta_evt+0x345b/0x39c0 net/bluetooth/hci_event.c:5645
hci_event_packet+0x1a29/0x858f net/bluetooth/hci_event.c:5885
hci_rx_work+0x46b/0xa90 net/bluetooth/hci_core.c:4359
process_one_work+0x864/0x1570 kernel/workqueue.c:2155
worker_thread+0x64c/0x1130 kernel/workqueue.c:2298
kthread+0x30b/0x410 kernel/kthread.c:246
ret_from_fork+0x24/0x30 arch/x86/entry/entry_64.S:415
Allocated by task 6440:
__do_kmalloc_node mm/slab.c:3689 [inline]
__kmalloc_node_track_caller+0x4c/0x70 mm/slab.c:3703
__kmalloc_reserve net/core/skbuff.c:137 [inline]
__alloc_skb+0xae/0x560 net/core/skbuff.c:205
alloc_skb include/linux/skbuff.h:995 [inline]
bt_skb_alloc include/net/bluetooth/bluetooth.h:339 [inline]
vhci_get_user drivers/bluetooth/hci_vhci.c:180 [inline]
vhci_write+0xbd/0x450 drivers/bluetooth/hci_vhci.c:299
call_write_iter include/linux/fs.h:1821 [inline]
new_sync_write fs/read_write.c:474 [inline]
__vfs_write+0x51b/0x770 fs/read_write.c:487
vfs_write+0x1f3/0x540 fs/read_write.c:549
ksys_write+0x12b/0x2a0 fs/read_write.c:599
do_syscall_64+0xf9/0x620 arch/x86/entry/common.c:293
entry_SYSCALL_64_after_hwframe+0x49/0xbe
Freed by task 4492:
__cache_free mm/slab.c:3503 [inline]
kfree+0xcc/0x210 mm/slab.c:3822
kernfs_fop_release+0x120/0x190 fs/kernfs/file.c:783
__fput+0x2ce/0x890 fs/file_table.c:278
task_work_run+0x148/0x1c0 kernel/task_work.c:113
tracehook_notify_resume include/linux/tracehook.h:193 [inline]
exit_to_usermode_loop+0x251/0x2a0 arch/x86/entry/common.c:167
prepare_exit_to_usermode arch/x86/entry/common.c:198 [inline]
syscall_return_slowpath arch/x86/entry/common.c:271 [inline]
do_syscall_64+0x538/0x620 arch/x86/entry/common.c:296
entry_SYSCALL_64_after_hwframe+0x49/0xbe
The buggy address belongs to the object at ffff8880a8741800
which belongs to the cache kmalloc-512 of size 512
The buggy address is located 21 bytes to the right of
512-byte region [ffff8880a8741800, ffff8880a8741a00)
The buggy address belongs to the page:
page:ffffea0002a1d040 count:1 mapcount:0 mapping:ffff88812c39c940 index:0x0
flags: 0xfffe0000000100(slab)
raw: 00fffe0000000100 ffffea0002a2b308 ffffea0002a31f88 ffff88812c39c940
raw: 0000000000000000 ffff8880a8741080 0000000100000006 0000000000000000
page dumped because: kasan: bad access detected
Memory state around the buggy address:
ffff8880a8741900: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
ffff8880a8741980: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>ffff8880a8741a00: fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc
^
ffff8880a8741a80: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb
ffff8880a8741b00: 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 can test patches for this issue, for details see:
https://goo.gl/tpsmEJ#testing-patches
syzbot found the following issue on:
HEAD commit: 205a42ce Linux 4.19.135
git tree: linux-4.19.y
console output: https://syzkaller.appspot.com/x/log.txt?x=13c87b60900000
kernel config: https://syzkaller.appspot.com/x/.config?x=155b0b328eb5e700
dashboard link: https://syzkaller.appspot.com/bug?extid=fbbeeb520a74f5c346d1
compiler: gcc (GCC) 10.1.0-syz 20200507
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1502f69b100000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=13379f12900000
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+fbbeeb...@syzkaller.appspotmail.com
IPVS: ftp: loaded support on port[0] = 21
Bluetooth: Unknown advertising packet type: 0xffff
Bluetooth: hci0: advertising data len corrected
Bluetooth: hci0: advertising data len corrected
==================================================================
BUG: KASAN: slab-out-of-bounds in hci_le_ext_adv_report_evt net/bluetooth/hci_event.c:5403 [inline]
BUG: KASAN: slab-out-of-bounds in hci_le_meta_evt+0x345b/0x39c0 net/bluetooth/hci_event.c:5645
Read of size 1 at addr ffff8880a8741a15 by task kworker/u5:2/6466
CPU: 0 PID: 6466 Comm: kworker/u5:2 Not tainted 4.19.135-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
Workqueue: hci0 hci_rx_work
Call Trace:
__dump_stack lib/dump_stack.c:77 [inline]
dump_stack+0x1fc/0x2fe lib/dump_stack.c:118
print_address_description.cold+0x54/0x219 mm/kasan/report.c:256
kasan_report_error.cold+0x8a/0x1c7 mm/kasan/report.c:354
kasan_report mm/kasan/report.c:412 [inline]
__asan_report_load1_noabort+0x88/0x90 mm/kasan/report.c:430
hci_le_ext_adv_report_evt net/bluetooth/hci_event.c:5403 [inline]
hci_le_meta_evt+0x345b/0x39c0 net/bluetooth/hci_event.c:5645
hci_event_packet+0x1a29/0x858f net/bluetooth/hci_event.c:5885
hci_rx_work+0x46b/0xa90 net/bluetooth/hci_core.c:4359
process_one_work+0x864/0x1570 kernel/workqueue.c:2155
worker_thread+0x64c/0x1130 kernel/workqueue.c:2298
kthread+0x30b/0x410 kernel/kthread.c:246
ret_from_fork+0x24/0x30 arch/x86/entry/entry_64.S:415
Allocated by task 6440:
__do_kmalloc_node mm/slab.c:3689 [inline]
__kmalloc_node_track_caller+0x4c/0x70 mm/slab.c:3703
__kmalloc_reserve net/core/skbuff.c:137 [inline]
__alloc_skb+0xae/0x560 net/core/skbuff.c:205
alloc_skb include/linux/skbuff.h:995 [inline]
bt_skb_alloc include/net/bluetooth/bluetooth.h:339 [inline]
vhci_get_user drivers/bluetooth/hci_vhci.c:180 [inline]
vhci_write+0xbd/0x450 drivers/bluetooth/hci_vhci.c:299
call_write_iter include/linux/fs.h:1821 [inline]
new_sync_write fs/read_write.c:474 [inline]
__vfs_write+0x51b/0x770 fs/read_write.c:487
vfs_write+0x1f3/0x540 fs/read_write.c:549
ksys_write+0x12b/0x2a0 fs/read_write.c:599
do_syscall_64+0xf9/0x620 arch/x86/entry/common.c:293
entry_SYSCALL_64_after_hwframe+0x49/0xbe
Freed by task 4492:
__cache_free mm/slab.c:3503 [inline]
kfree+0xcc/0x210 mm/slab.c:3822
kernfs_fop_release+0x120/0x190 fs/kernfs/file.c:783
__fput+0x2ce/0x890 fs/file_table.c:278
task_work_run+0x148/0x1c0 kernel/task_work.c:113
tracehook_notify_resume include/linux/tracehook.h:193 [inline]
exit_to_usermode_loop+0x251/0x2a0 arch/x86/entry/common.c:167
prepare_exit_to_usermode arch/x86/entry/common.c:198 [inline]
syscall_return_slowpath arch/x86/entry/common.c:271 [inline]
do_syscall_64+0x538/0x620 arch/x86/entry/common.c:296
entry_SYSCALL_64_after_hwframe+0x49/0xbe
The buggy address belongs to the object at ffff8880a8741800
which belongs to the cache kmalloc-512 of size 512
The buggy address is located 21 bytes to the right of
512-byte region [ffff8880a8741800, ffff8880a8741a00)
The buggy address belongs to the page:
page:ffffea0002a1d040 count:1 mapcount:0 mapping:ffff88812c39c940 index:0x0
flags: 0xfffe0000000100(slab)
raw: 00fffe0000000100 ffffea0002a2b308 ffffea0002a31f88 ffff88812c39c940
raw: 0000000000000000 ffff8880a8741080 0000000100000006 0000000000000000
page dumped because: kasan: bad access detected
Memory state around the buggy address:
ffff8880a8741900: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
ffff8880a8741980: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>ffff8880a8741a00: fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc
^
ffff8880a8741a80: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb
ffff8880a8741b00: 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 can test patches for this issue, for details see:
https://goo.gl/tpsmEJ#testing-patches
syzbot
Aug 2, 2020, 8:19:15 AM8/2/20
to syzkaller...@googlegroups.com
Hello,
syzbot found the following issue on:
HEAD commit: 7f2c5eb4 Linux 4.14.191
syzbot found the following issue on:
git tree: linux-4.14.y
console output: https://syzkaller.appspot.com/x/log.txt?x=156c7b60900000
kernel config: https://syzkaller.appspot.com/x/.config?x=881f1aee9620bf9f
dashboard link: https://syzkaller.appspot.com/bug?extid=46682331b57dc6fd00d4
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:
Bluetooth: Unknown advertising packet type: 0xff
==================================================================
BUG: KASAN: slab-out-of-bounds in hci_le_adv_report_evt net/bluetooth/hci_event.c:4945 [inline]
BUG: KASAN: slab-out-of-bounds in hci_le_meta_evt+0x3763/0x3fc0 net/bluetooth/hci_event.c:5169
Read of size 1 at addr ffff888096f7d204 by task kworker/u5:4/7815
CPU: 1 PID: 7815 Comm: kworker/u5:4 Not tainted 4.14.191-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
Workqueue: hci3 hci_rx_work
Call Trace:
__dump_stack lib/dump_stack.c:17 [inline]
dump_stack+0x1b2/0x283 lib/dump_stack.c:58
print_address_description.cold+0x54/0x1d3 mm/kasan/report.c:252
kasan_report_error.cold+0x8a/0x194 mm/kasan/report.c:351
kasan_report mm/kasan/report.c:409 [inline]
__asan_report_load1_noabort+0x68/0x70 mm/kasan/report.c:427
hci_le_adv_report_evt net/bluetooth/hci_event.c:4945 [inline]
hci_le_meta_evt+0x3763/0x3fc0 net/bluetooth/hci_event.c:5169
hci_event_packet+0x25a7/0x7c7a net/bluetooth/hci_event.c:5416
hci_rx_work+0x3e6/0x970 net/bluetooth/hci_core.c:4244
process_one_work+0x793/0x14a0 kernel/workqueue.c:2116
worker_thread+0x5cc/0xff0 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 12256:
save_stack mm/kasan/kasan.c:447 [inline]
set_track mm/kasan/kasan.c:459 [inline]
kasan_kmalloc+0xeb/0x160 mm/kasan/kasan.c:551
__do_kmalloc_node mm/slab.c:3682 [inline]
__kmalloc_node_track_caller+0x4c/0x70 mm/slab.c:3696
__kmalloc_reserve net/core/skbuff.c:137 [inline]
__alloc_skb+0x96/0x510 net/core/skbuff.c:205
alloc_skb include/linux/skbuff.h:980 [inline]
bt_skb_alloc include/net/bluetooth/bluetooth.h:336 [inline]
vhci_get_user drivers/bluetooth/hci_vhci.c:180 [inline]
vhci_write+0xb1/0x420 drivers/bluetooth/hci_vhci.c:299
call_write_iter include/linux/fs.h:1778 [inline]
new_sync_write fs/read_write.c:469 [inline]
__vfs_write+0x44c/0x630 fs/read_write.c:482
vfs_write+0x17f/0x4d0 fs/read_write.c:544
SYSC_write fs/read_write.c:590 [inline]
SyS_write+0xf2/0x210 fs/read_write.c:582
do_syscall_64+0x1d5/0x640 arch/x86/entry/common.c:292
entry_SYSCALL_64_after_hwframe+0x46/0xbb
Freed by task 3662:
save_stack mm/kasan/kasan.c:447 [inline]
set_track mm/kasan/kasan.c:459 [inline]
kasan_slab_free+0xc3/0x1a0 mm/kasan/kasan.c:524
__cache_free mm/slab.c:3496 [inline]
kfree+0xc9/0x250 mm/slab.c:3815
skb_free_head net/core/skbuff.c:554 [inline]
skb_release_data+0x5f6/0x820 net/core/skbuff.c:574
skb_release_all net/core/skbuff.c:631 [inline]
__kfree_skb net/core/skbuff.c:645 [inline]
consume_skb+0xe0/0x380 net/core/skbuff.c:705
skb_free_datagram+0x16/0xe0 net/core/datagram.c:331
unix_dgram_recvmsg+0x663/0xd10 net/unix/af_unix.c:2207
sock_recvmsg_nosec net/socket.c:819 [inline]
sock_recvmsg net/socket.c:826 [inline]
sock_recvmsg+0xc0/0x100 net/socket.c:822
___sys_recvmsg+0x20b/0x4d0 net/socket.c:2221
__sys_recvmsg+0xa0/0x120 net/socket.c:2266
SYSC_recvmsg net/socket.c:2278 [inline]
SyS_recvmsg+0x27/0x40 net/socket.c:2273
do_syscall_64+0x1d5/0x640 arch/x86/entry/common.c:292
entry_SYSCALL_64_after_hwframe+0x46/0xbb
The buggy address belongs to the object at ffff888096f7d000
which belongs to the cache kmalloc-512 of size 512
The buggy address is located 4 bytes to the right of
512-byte region [ffff888096f7d000, ffff888096f7d200)
The buggy address belongs to the page:
page:ffffea00025bdf40 count:1 mapcount:0 mapping:ffff888096f7d000 index:0xffff888096f7da00
flags: 0xfffe0000000100(slab)
raw: 00fffe0000000100 ffff888096f7d000 ffff888096f7da00 0000000100000004
raw: ffffea00024a2e20 ffffea0002470aa0 ffff88812fe52940 0000000000000000
page dumped because: kasan: bad access detected
Memory state around the buggy address:
ffff888096f7d100: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Memory state around the buggy address:
ffff888096f7d180: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>ffff888096f7d200: fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc
^
ffff888096f7d280: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb
ffff888096f7d300: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb
syzbot
Aug 2, 2020, 8:32:16 AM8/2/20
to syzkaller...@googlegroups.com
syzbot has found a reproducer for the following issue on:
HEAD commit: 7f2c5eb4 Linux 4.14.191
git tree: linux-4.14.y
console output: https://syzkaller.appspot.com/x/log.txt?x=15e31acc900000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=120e2878900000
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+466823...@syzkaller.appspotmail.com
audit: type=1400 audit(1596371376.702:8): avc: denied { execmem } for pid=6362 comm="syz-executor424" scontext=system_u:system_r:kernel_t:s0 tcontext=system_u:system_r:kernel_t:s0 tclass=process permissive=1
CPU: 0 PID: 6387 Comm: kworker/u5:1 Not tainted 4.14.191-syzkaller #0
__fput+0x25f/0x7a0 fs/file_table.c:210
task_work_run+0x11f/0x190 kernel/task_work.c:113
tracehook_notify_resume include/linux/tracehook.h:191 [inline]
exit_to_usermode_loop+0x1ad/0x200 arch/x86/entry/common.c:164
prepare_exit_to_usermode arch/x86/entry/common.c:199 [inline]
syscall_return_slowpath arch/x86/entry/common.c:270 [inline]
do_syscall_64+0x4a3/0x640 arch/x86/entry/common.c:297
entry_SYSCALL_64_after_hwframe+0x46/0xbb
The buggy address belongs to the object at ffff8880a60830c0
flags: 0xfffe0000000100(slab)
raw: 00fffe0000000100 ffff8880a60830c0 ffff8880a6083ac0 0000000100000002
raw: ffffea00029814a0 ffffea0002a37620 ffff88812fe52940 0000000000000000
ffff8880a6083200: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>ffff8880a6083280: 00 00 00 00 00 00 00 00 fc fc fc fc fc fc fc fc
^
ffff8880a6083300: fc fc fc fc fc fc fc fc fb fb fb fb fb fb fb fb
ffff8880a6083380: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb
==================================================================
HEAD commit: 7f2c5eb4 Linux 4.14.191
git tree: linux-4.14.y
kernel config: https://syzkaller.appspot.com/x/.config?x=881f1aee9620bf9f
dashboard link: https://syzkaller.appspot.com/bug?extid=46682331b57dc6fd00d4
compiler: gcc (GCC) 10.1.0-syz 20200507
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1151790c900000
dashboard link: https://syzkaller.appspot.com/bug?extid=46682331b57dc6fd00d4
compiler: gcc (GCC) 10.1.0-syz 20200507
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=120e2878900000
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+466823...@syzkaller.appspotmail.com
IPVS: ftp: loaded support on port[0] = 21
Bluetooth: Unknown advertising packet type: 0xff
Bluetooth: hci0 advertising data length corrected
==================================================================
BUG: KASAN: slab-out-of-bounds in hci_le_adv_report_evt net/bluetooth/hci_event.c:4945 [inline]
BUG: KASAN: slab-out-of-bounds in hci_le_meta_evt+0x3763/0x3fc0 net/bluetooth/hci_event.c:5169
Read of size 1 at addr ffff8880a60832c4 by task kworker/u5:1/6387
BUG: KASAN: slab-out-of-bounds in hci_le_adv_report_evt net/bluetooth/hci_event.c:4945 [inline]
BUG: KASAN: slab-out-of-bounds in hci_le_meta_evt+0x3763/0x3fc0 net/bluetooth/hci_event.c:5169
CPU: 0 PID: 6387 Comm: kworker/u5:1 Not tainted 4.14.191-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
Workqueue: hci0 hci_rx_work
Call Trace:
__dump_stack lib/dump_stack.c:17 [inline]
dump_stack+0x1b2/0x283 lib/dump_stack.c:58
print_address_description.cold+0x54/0x1d3 mm/kasan/report.c:252
kasan_report_error.cold+0x8a/0x194 mm/kasan/report.c:351
kasan_report mm/kasan/report.c:409 [inline]
__asan_report_load1_noabort+0x68/0x70 mm/kasan/report.c:427
hci_le_adv_report_evt net/bluetooth/hci_event.c:4945 [inline]
hci_le_meta_evt+0x3763/0x3fc0 net/bluetooth/hci_event.c:5169
hci_event_packet+0x25a7/0x7c7a net/bluetooth/hci_event.c:5416
hci_rx_work+0x3e6/0x970 net/bluetooth/hci_core.c:4244
process_one_work+0x793/0x14a0 kernel/workqueue.c:2116
worker_thread+0x5cc/0xff0 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 6392:
__dump_stack lib/dump_stack.c:17 [inline]
dump_stack+0x1b2/0x283 lib/dump_stack.c:58
print_address_description.cold+0x54/0x1d3 mm/kasan/report.c:252
kasan_report_error.cold+0x8a/0x194 mm/kasan/report.c:351
kasan_report mm/kasan/report.c:409 [inline]
__asan_report_load1_noabort+0x68/0x70 mm/kasan/report.c:427
hci_le_adv_report_evt net/bluetooth/hci_event.c:4945 [inline]
hci_le_meta_evt+0x3763/0x3fc0 net/bluetooth/hci_event.c:5169
hci_event_packet+0x25a7/0x7c7a net/bluetooth/hci_event.c:5416
hci_rx_work+0x3e6/0x970 net/bluetooth/hci_core.c:4244
process_one_work+0x793/0x14a0 kernel/workqueue.c:2116
worker_thread+0x5cc/0xff0 kernel/workqueue.c:2250
kthread+0x30d/0x420 kernel/kthread.c:232
ret_from_fork+0x24/0x30 arch/x86/entry/entry_64.S:404
save_stack mm/kasan/kasan.c:447 [inline]
set_track mm/kasan/kasan.c:459 [inline]
kasan_kmalloc+0xeb/0x160 mm/kasan/kasan.c:551
__do_kmalloc_node mm/slab.c:3682 [inline]
__kmalloc_node_track_caller+0x4c/0x70 mm/slab.c:3696
__kmalloc_reserve net/core/skbuff.c:137 [inline]
__alloc_skb+0x96/0x510 net/core/skbuff.c:205
alloc_skb include/linux/skbuff.h:980 [inline]
bt_skb_alloc include/net/bluetooth/bluetooth.h:336 [inline]
vhci_get_user drivers/bluetooth/hci_vhci.c:180 [inline]
vhci_write+0xb1/0x420 drivers/bluetooth/hci_vhci.c:299
call_write_iter include/linux/fs.h:1778 [inline]
new_sync_write fs/read_write.c:469 [inline]
__vfs_write+0x44c/0x630 fs/read_write.c:482
vfs_write+0x17f/0x4d0 fs/read_write.c:544
SYSC_write fs/read_write.c:590 [inline]
SyS_write+0xf2/0x210 fs/read_write.c:582
do_syscall_64+0x1d5/0x640 arch/x86/entry/common.c:292
entry_SYSCALL_64_after_hwframe+0x46/0xbb
Freed by task 4675:
set_track mm/kasan/kasan.c:459 [inline]
kasan_kmalloc+0xeb/0x160 mm/kasan/kasan.c:551
__do_kmalloc_node mm/slab.c:3682 [inline]
__kmalloc_node_track_caller+0x4c/0x70 mm/slab.c:3696
__kmalloc_reserve net/core/skbuff.c:137 [inline]
__alloc_skb+0x96/0x510 net/core/skbuff.c:205
alloc_skb include/linux/skbuff.h:980 [inline]
bt_skb_alloc include/net/bluetooth/bluetooth.h:336 [inline]
vhci_get_user drivers/bluetooth/hci_vhci.c:180 [inline]
vhci_write+0xb1/0x420 drivers/bluetooth/hci_vhci.c:299
call_write_iter include/linux/fs.h:1778 [inline]
new_sync_write fs/read_write.c:469 [inline]
__vfs_write+0x44c/0x630 fs/read_write.c:482
vfs_write+0x17f/0x4d0 fs/read_write.c:544
SYSC_write fs/read_write.c:590 [inline]
SyS_write+0xf2/0x210 fs/read_write.c:582
do_syscall_64+0x1d5/0x640 arch/x86/entry/common.c:292
entry_SYSCALL_64_after_hwframe+0x46/0xbb
save_stack mm/kasan/kasan.c:447 [inline]
set_track mm/kasan/kasan.c:459 [inline]
kasan_slab_free+0xc3/0x1a0 mm/kasan/kasan.c:524
__cache_free mm/slab.c:3496 [inline]
kfree+0xc9/0x250 mm/slab.c:3815
kernfs_fop_release+0x10e/0x180 fs/kernfs/file.c:783
set_track mm/kasan/kasan.c:459 [inline]
kasan_slab_free+0xc3/0x1a0 mm/kasan/kasan.c:524
__cache_free mm/slab.c:3496 [inline]
kfree+0xc9/0x250 mm/slab.c:3815
__fput+0x25f/0x7a0 fs/file_table.c:210
task_work_run+0x11f/0x190 kernel/task_work.c:113
tracehook_notify_resume include/linux/tracehook.h:191 [inline]
exit_to_usermode_loop+0x1ad/0x200 arch/x86/entry/common.c:164
prepare_exit_to_usermode arch/x86/entry/common.c:199 [inline]
syscall_return_slowpath arch/x86/entry/common.c:270 [inline]
do_syscall_64+0x4a3/0x640 arch/x86/entry/common.c:297
entry_SYSCALL_64_after_hwframe+0x46/0xbb
The buggy address belongs to the object at ffff8880a60830c0
which belongs to the cache kmalloc-512 of size 512
The buggy address is located 4 bytes to the right of
512-byte region [ffff8880a60830c0, ffff8880a60832c0)
The buggy address is located 4 bytes to the right of
The buggy address belongs to the page:
page:ffffea00029820c0 count:1 mapcount:0 mapping:ffff8880a60830c0 index:0xffff8880a6083ac0
flags: 0xfffe0000000100(slab)
raw: 00fffe0000000100 ffff8880a60830c0 ffff8880a6083ac0 0000000100000002
raw: ffffea00029814a0 ffffea0002a37620 ffff88812fe52940 0000000000000000
page dumped because: kasan: bad access detected
Memory state around the buggy address:
ffff8880a6083180: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Memory state around the buggy address:
ffff8880a6083200: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>ffff8880a6083280: 00 00 00 00 00 00 00 00 fc fc fc fc fc fc fc fc
^
ffff8880a6083300: fc fc fc fc fc fc fc fc fb fb fb fb fb fb fb fb
ffff8880a6083380: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb
==================================================================
syzbot
Dec 30, 2020, 2:32:08 AM12/30/20
to syzkaller...@googlegroups.com
syzbot suspects this issue was fixed by commit:
commit 7ee2cd49f7220b1069e23a65d3ab59526bda9821
Author: Peilin Ye <yepei...@gmail.com>
Date: Wed Sep 9 07:17:00 2020 +0000
Bluetooth: Fix slab-out-of-bounds read in hci_le_direct_adv_report_evt()
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=15b1f8db500000
start commit: d7e78d08 Linux 4.14.195
git tree: linux-4.14.y
kernel config: https://syzkaller.appspot.com/x/.config?x=6608b656f49b4e8c
dashboard link: https://syzkaller.appspot.com/bug?extid=46682331b57dc6fd00d4
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=15c57751900000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=13a9c346900000
If the result looks correct, please mark the issue as fixed by replying with:
#syz fix: Bluetooth: Fix slab-out-of-bounds read in hci_le_direct_adv_report_evt()
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
commit 7ee2cd49f7220b1069e23a65d3ab59526bda9821
Author: Peilin Ye <yepei...@gmail.com>
Date: Wed Sep 9 07:17:00 2020 +0000
Bluetooth: Fix slab-out-of-bounds read in hci_le_direct_adv_report_evt()
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=15b1f8db500000
start commit: d7e78d08 Linux 4.14.195
git tree: linux-4.14.y
kernel config: https://syzkaller.appspot.com/x/.config?x=6608b656f49b4e8c
dashboard link: https://syzkaller.appspot.com/bug?extid=46682331b57dc6fd00d4
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=15c57751900000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=13a9c346900000
If the result looks correct, please mark the issue as fixed by replying with:
#syz fix: Bluetooth: Fix slab-out-of-bounds read in hci_le_direct_adv_report_evt()
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
syzbot
Jan 18, 2021, 8:09:12 AM1/18/21
to syzkaller...@googlegroups.com
syzbot suspects this issue was fixed by commit:
commit 61490c481c61ff230da5f6042f353c6c0db0bc0c
Author: Peilin Ye <yepei...@gmail.com>
Date: Wed Sep 9 07:17:00 2020 +0000
Bluetooth: Fix slab-out-of-bounds read in hci_le_direct_adv_report_evt()
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=168e5e68d00000
Date: Wed Sep 9 07:17:00 2020 +0000
Bluetooth: Fix slab-out-of-bounds read in hci_le_direct_adv_report_evt()
start commit: f6d5cb9e Linux 4.19.142
git tree: linux-4.19.y
kernel config: https://syzkaller.appspot.com/x/.config?x=30067df04d3254aa
dashboard link: https://syzkaller.appspot.com/bug?extid=fbbeeb520a74f5c346d1
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=13a9e996900000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1452ce61900000
Reply all
Reply to author
Forward
0 new messages