syzbot


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

Status: auto-closed as invalid on 2021/08/30 12:28
Reported-by: syzbot+90682d1565b1a02e7b37@syzkaller.appspotmail.com
First crash: 1106d, last: 1030d
Similar bugs (8)
Kernel Title Repro Cause bisect Fix bisect Count Last Reported Patched Status
upstream KASAN: use-after-free Write in skb_release_data net C 1903 2103d 2155d 8/26 fixed on 2018/08/07 13:43
android-414 KASAN: use-after-free Write in skb_release_data 3 1594d 1673d 0/1 auto-closed as invalid on 2020/02/13 13:09
linux-4.19 KASAN: use-after-free Write in skb_release_data 1 1415d 1415d 0/1 auto-closed as invalid on 2020/08/10 01:37
upstream KASAN: use-after-free Write in skb_release_data (2) net C done unreliable 875 900d 1960d 0/26 auto-obsoleted due to no activity on 2023/04/16 03:59
android-54 KASAN: use-after-free Write in skb_release_data 2 1306d 1337d 0/2 auto-closed as invalid on 2020/11/26 21:03
upstream KMSAN: uninit-value in skb_release_data (3) net C 10 586d 1265d 0/26 auto-obsoleted due to no activity on 2022/11/17 07:20
linux-5.15 KASAN: use-after-free Read in skb_release_data 1 324d 324d 0/3 auto-obsoleted due to no activity on 2023/08/06 13:46
upstream general protection fault in skb_release_data (2) net C done error 521 216d 1265d 0/26 upstream: reported C repro on 2020/09/09 09:58

Sample crash report:
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 include/asm-generic/atomic-instrumented.h:305 [inline]
BUG: KASAN: use-after-free in skb_release_data+0x120/0x920 net/core/skbuff.c:572
Write of size 4 at addr ffff88809b63f360 by task syz-executor.4/12181

CPU: 1 PID: 12181 Comm: syz-executor.4 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+0x8f/0xa0 mm/kasan/report.c:412
 atomic_sub_return include/asm-generic/atomic-instrumented.h:305 [inline]
 skb_release_data+0x120/0x920 net/core/skbuff.c:572
 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_dev_open+0x130/0x250 net/bluetooth/hci_core.c:1577
 hci_sock_ioctl+0x57e/0x7d0 net/bluetooth/hci_sock.c:1018
 sock_do_ioctl+0xcb/0x2d0 net/socket.c:950
 sock_ioctl+0x2ef/0x5d0 net/socket.c:1074
 vfs_ioctl fs/ioctl.c:46 [inline]
 file_ioctl fs/ioctl.c:501 [inline]
 do_vfs_ioctl+0xcdb/0x12e0 fs/ioctl.c:688
 ksys_ioctl+0x9b/0xc0 fs/ioctl.c:705
 __do_sys_ioctl fs/ioctl.c:712 [inline]
 __se_sys_ioctl fs/ioctl.c:710 [inline]
 __x64_sys_ioctl+0x6f/0xb0 fs/ioctl.c:710
 do_syscall_64+0xf9/0x620 arch/x86/entry/common.c:293
 entry_SYSCALL_64_after_hwframe+0x49/0xbe
RIP: 0033:0x4663b7
Code: 3c 1c 48 f7 d8 49 39 c4 72 b8 e8 a4 48 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:00007ffdb97a96b8 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 00000000034a43bc RCX: 00000000004663b7
RDX: 0000000000000004 RSI: 00000000400448c9 RDI: 0000000000000003
RBP: 0000000000000003 R08: 0000000000000000 R09: 00007f295a2f9700
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000004
R13: 000000000056ca68 R14: 0000000000000000 R15: 00000000000000f8

Allocated by task 12181:
 __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
 bredr_setup net/bluetooth/hci_core.c:293 [inline]
 hci_init2_req+0x667/0x8b0 net/bluetooth/hci_core.c:422
 __hci_req_sync+0x133/0x8a0 net/bluetooth/hci_request.c:205
 __hci_init net/bluetooth/hci_core.c:874 [inline]
 hci_dev_do_open+0xe0d/0x1260 net/bluetooth/hci_core.c:1465
 hci_dev_open+0x130/0x250 net/bluetooth/hci_core.c:1577
 hci_sock_ioctl+0x57e/0x7d0 net/bluetooth/hci_sock.c:1018
 sock_do_ioctl+0xcb/0x2d0 net/socket.c:950
 sock_ioctl+0x2ef/0x5d0 net/socket.c:1074
 vfs_ioctl fs/ioctl.c:46 [inline]
 file_ioctl fs/ioctl.c:501 [inline]
 do_vfs_ioctl+0xcdb/0x12e0 fs/ioctl.c:688
 ksys_ioctl+0x9b/0xc0 fs/ioctl.c:705
 __do_sys_ioctl fs/ioctl.c:712 [inline]
 __se_sys_ioctl fs/ioctl.c:710 [inline]
 __x64_sys_ioctl+0x6f/0xb0 fs/ioctl.c:710
 do_syscall_64+0xf9/0x620 arch/x86/entry/common.c:293
 entry_SYSCALL_64_after_hwframe+0x49/0xbe

Freed by task 8156:
 __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_cmd_work+0x182/0x360 net/bluetooth/hci_core.c:4395
 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 ffff88809b63f280
 which belongs to the cache kmalloc-512 of size 512
The buggy address is located 224 bytes inside of
 512-byte region [ffff88809b63f280, ffff88809b63f480)
The buggy address belongs to the page:
page:ffffea00026d8fc0 count:1 mapcount:0 mapping:ffff88813bff0940 index:0xffff88809b63fc80
flags: 0xfff00000000100(slab)
raw: 00fff00000000100 ffffea0002619308 ffffea0002940cc8 ffff88813bff0940
raw: ffff88809b63fc80 ffff88809b63f000 0000000100000005 0000000000000000
page dumped because: kasan: bad access detected

Memory state around the buggy address:
 ffff88809b63f200: fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc
 ffff88809b63f280: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb
>ffff88809b63f300: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb
                                                       ^
 ffff88809b63f380: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb
 ffff88809b63f400: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb
==================================================================

Crashes (3):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2021/05/02 12:27 linux-4.19.y 97a8651cadce 77e2b668 .config console log report info ci2-linux-4-19 KASAN: use-after-free Write in skb_release_data
2021/03/16 00:19 linux-4.19.y 030194a5b292 fdb2bb2c .config console log report info ci2-linux-4-19 KASAN: use-after-free Write in skb_release_data
2021/02/15 01:47 linux-4.19.y 811218eceeaa 98682e5e .config console log report info ci2-linux-4-19 KASAN: use-after-free Write in skb_release_data
* Struck through repros no longer work on HEAD.