syzbot

 sign-in | mailing list | source | docs
🐞 Open [712]
🐞 Fixed [297]
🐞 Invalid [838]
≡ Crashes
Kernel Health Bugs/Month Bug Lifetimes Fuzzing
💬 Send us feedback

KASAN: use-after-free Read in hci_cmd_timeout

Status: upstream: reported syz repro on 2019/09/01 02:37
Reported-by: syzbot+fba50ca40cd875b49388@syzkaller.appspotmail.com
First crash: 2125d, last: 878d
Fix bisection: failed (error log, bisect log)
  
▶ ▼ Similar bugs (5)
Kernel Title Repro Cause bisect Fix bisect Count Last Reported Patched Status
android-5-10 KASAN: use-after-free Read in hci_cmd_timeout 1 849d 849d 0/2 auto-obsoleted due to no activity on 2023/05/29 20:38
linux-6.1 KASAN: use-after-free Read in hci_cmd_timeout 4 227d 319d 0/3 auto-obsoleted due to no activity on 2025/02/19 13:57
linux-4.14 KASAN: use-after-free Read in hci_cmd_timeout C inconclusive 11 1256d 2120d 0/1 upstream: reported C repro on 2019/09/06 20:31
upstream KASAN: use-after-free Read in hci_cmd_timeout C done error 371 930d 2242d 22/29 fixed on 2023/04/12 21:18
upstream KASAN: slab-use-after-free Read in hci_cmd_timeout bluetooth 28 320d 467d 0/29 auto-obsoleted due to no activity on 2024/10/24 09:00
▶ ▼ Fix bisection attempts (7)
Created Duration User Patch Repo Result
2020/08/18 02:48 20m bisect fix linux-4.19.y error job log
2020/06/26 19:09 37m bisect fix linux-4.19.y OK (0) job log log
2020/05/27 17:13 38m bisect fix linux-4.19.y OK (0) job log log
2020/04/27 16:34 38m bisect fix linux-4.19.y OK (0) job log log
2020/03/28 15:57 37m bisect fix linux-4.19.y OK (0) job log log
2020/02/27 15:14 42m bisect fix linux-4.19.y OK (0) job log log
2020/01/28 14:20 40m bisect fix linux-4.19.y OK (0) job log log

Sample crash report:
Bluetooth: hci8: Entering manufacturer mode failed (-110)
Bluetooth: hci8: sending frame failed (-49)
Bluetooth: hci10: Entering manufacturer mode failed (-110)
Bluetooth: hci9: Entering manufacturer mode failed (-110)
==================================================================
BUG: KASAN: use-after-free in hci_cmd_timeout+0x1ae/0x1c0 net/bluetooth/hci_core.c:2576
Read of size 2 at addr ffff888096c9d348 by task kworker/0:0/5

CPU: 0 PID: 5 Comm: kworker/0:0 Not tainted 4.19.187-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
Workqueue: events hci_cmd_timeout
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_load_n_noabort+0x8b/0xa0 mm/kasan/report.c:443
 hci_cmd_timeout+0x1ae/0x1c0 net/bluetooth/hci_core.c:2576
 process_one_work+0x864/0x1570 kernel/workqueue.c:2152
 worker_thread+0x64c/0x1130 kernel/workqueue.c:2295
 kthread+0x33f/0x460 kernel/kthread.c:259
 ret_from_fork+0x24/0x30 arch/x86/entry/entry_64.S:415

Allocated by task 8162:
 __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]
 hci_prepare_cmd+0x2a/0x290 net/bluetooth/hci_request.c:292
 hci_req_add_ev+0xdc/0x220 net/bluetooth/hci_request.c:326
 __hci_cmd_sync_ev+0x119/0x670 net/bluetooth/hci_request.c:138
 btintel_enter_mfg+0x2a/0x90 drivers/bluetooth/btintel.c:82
 ag6xx_setup+0xfc/0x790 drivers/bluetooth/hci_ag6xx.c:180
 hci_uart_setup+0x1b1/0x470 drivers/bluetooth/hci_ldisc.c:431
 hci_dev_do_open+0x360/0x1260 net/bluetooth/hci_core.c:1425
 hci_power_on+0x117/0x530 net/bluetooth/hci_core.c:2132
 process_one_work+0x864/0x1570 kernel/workqueue.c:2152
 worker_thread+0x64c/0x1130 kernel/workqueue.c:2295
 kthread+0x33f/0x460 kernel/kthread.c:259
 ret_from_fork+0x24/0x30 arch/x86/entry/entry_64.S:415

Freed by task 8162:
 __cache_free mm/slab.c:3503 [inline]
 kfree+0xcc/0x210 mm/slab.c:3822
 skb_free_head net/core/skbuff.c:563 [inline]
 skb_release_data+0x6de/0x920 net/core/skbuff.c:583
 skb_release_all net/core/skbuff.c:640 [inline]
 __kfree_skb net/core/skbuff.c:654 [inline]
 kfree_skb+0x11a/0x3d0 net/core/skbuff.c:672
 hci_dev_do_open+0xaf0/0x1260 net/bluetooth/hci_core.c:1511
 hci_power_on+0x117/0x530 net/bluetooth/hci_core.c:2132
 process_one_work+0x864/0x1570 kernel/workqueue.c:2152
 worker_thread+0x64c/0x1130 kernel/workqueue.c:2295
 kthread+0x33f/0x460 kernel/kthread.c:259
 ret_from_fork+0x24/0x30 arch/x86/entry/entry_64.S:415

The buggy address belongs to the object at ffff888096c9d340
 which belongs to the cache kmalloc-512 of size 512
The buggy address is located 8 bytes inside of
 512-byte region [ffff888096c9d340, ffff888096c9d540)
The buggy address belongs to the page:
page:ffffea00025b2740 count:1 mapcount:0 mapping:ffff88813bff0940 index:0x0
flags: 0xfff00000000100(slab)
raw: 00fff00000000100 ffffea0002d36588 ffffea0002d3efc8 ffff88813bff0940
raw: 0000000000000000 ffff888096c9d0c0 0000000100000006 0000000000000000
page dumped because: kasan: bad access detected

Memory state around the buggy address:
 ffff888096c9d200: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb
 ffff888096c9d280: fb fb fb fb fb fb fb fb fc fc fc fc fc fc fc fc
>ffff888096c9d300: fc fc fc fc fc fc fc fc fb fb fb fb fb fb fb fb
                                              ^
 ffff888096c9d380: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb
 ffff888096c9d400: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb
==================================================================
Bluetooth: hci11: Entering manufacturer mode failed (-110)

Crashes (17):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2021/04/15 03:53 linux-4.19.y 0f1b4cb77d7f fcdb12ba .config console log report syz ci2-linux-4-19 KASAN: use-after-free Read in hci_cmd_timeout
2020/07/05 12:13 linux-4.19.y 399849e4654e 24d7f505 .config console log report syz ci2-linux-4-19
2019/12/07 00:14 linux-4.19.y fb683b5e3f53 85f26751 .config console log report syz ci2-linux-4-19
2023/01/30 20:16 linux-4.19.y 3f8a27f9e27b b68fb8d6 .config console log report info [disk image] [vmlinux] ci2-linux-4-19 KASAN: use-after-free Read in hci_cmd_timeout
2022/11/10 15:46 linux-4.19.y 3f8a27f9e27b 3ead01ad .config console log report info [disk image] [vmlinux] ci2-linux-4-19 KASAN: use-after-free Read in hci_cmd_timeout
2022/10/28 09:02 linux-4.19.y 3f8a27f9e27b 5c716ff6 .config console log report info [disk image] [vmlinux] ci2-linux-4-19 KASAN: use-after-free Read in hci_cmd_timeout
2022/07/28 07:58 linux-4.19.y 3f8a27f9e27b fb95c74d .config console log report info ci2-linux-4-19 KASAN: use-after-free Read in hci_cmd_timeout
2022/05/19 13:29 linux-4.19.y 3f8a27f9e27b cb1ac2e7 .config console log report info ci2-linux-4-19 KASAN: use-after-free Read in hci_cmd_timeout
2022/02/27 12:06 linux-4.19.y 3f8a27f9e27b 45a13a73 .config console log report info ci2-linux-4-19 KASAN: use-after-free Read in hci_cmd_timeout
2021/09/21 13:20 linux-4.19.y b172b44fcb17 169724fe .config console log report info ci2-linux-4-19 KASAN: use-after-free Read in hci_cmd_timeout
2021/05/20 12:21 linux-4.19.y 3c8c23092588 c560a65d .config console log report info ci2-linux-4-19 KASAN: use-after-free Read in hci_cmd_timeout
2021/04/14 21:52 linux-4.19.y 0f1b4cb77d7f fcdb12ba .config console log report info ci2-linux-4-19 KASAN: use-after-free Read in hci_cmd_timeout
2021/03/04 06:02 linux-4.19.y 2d19be4653f5 d7e4e604 .config console log report info ci2-linux-4-19 KASAN: use-after-free Read in hci_cmd_timeout
2020/07/19 02:48 linux-4.19.y 17a87580a885 9c812472 .config console log report ci2-linux-4-19
2020/07/12 04:04 linux-4.19.y dce0f88600e4 7ba05d2d .config console log report ci2-linux-4-19
2019/12/29 11:13 linux-4.19.y 672481c2deff af6b8ef8 .config console log report ci2-linux-4-19
2019/09/01 01:36 linux-4.19.y 97ab07e11fbf bad3cce2 .config console log report ci2-linux-4-19
* Struck through repros no longer work on HEAD.