WARNING: ODEBUG bug in rfcomm_dev_ioctl

15 views
Skip to first unread message

syzbot

unread,
Mar 23, 2020, 2:04:18 PM3/23/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=1728dce5e00000
kernel config: https://syzkaller.appspot.com/x/.config?x=664dd71881ab2b2d
dashboard link: https://syzkaller.appspot.com/bug?extid=ed209d00d1a00ff450e8
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+ed209d...@syzkaller.appspotmail.com

audit: type=1400 audit(2000000022.890:63): avc: denied { map } for pid=9234 comm="syz-executor.5" path="/dev/ashmem" dev="devtmpfs" ino=17521 scontext=unconfined_u:system_r:insmod_t:s0-s0:c0.c1023 tcontext=system_u:object_r:device_t:s0 tclass=chr_file permissive=1
ip6_tables: ip6tables: counters copy to user failed while replacing table
ODEBUG: free active (active state 0) object type: timer_list hint: __write_once_size include/linux/compiler.h:210 [inline]
ODEBUG: free active (active state 0) object type: timer_list hint: __list_add include/linux/list.h:66 [inline]
ODEBUG: free active (active state 0) object type: timer_list hint: list_add include/linux/list.h:79 [inline]
ODEBUG: free active (active state 0) object type: timer_list hint: rfcomm_dlc_timeout+0x0/0x60 net/bluetooth/rfcomm/core.c:337
------------[ cut here ]------------
WARNING: CPU: 0 PID: 9250 at lib/debugobjects.c:287 debug_print_object.cold+0xa7/0xdb lib/debugobjects.c:287
Kernel panic - not syncing: panic_on_warn set ...

CPU: 0 PID: 9250 Comm: syz-executor.0 Not tainted 4.14.174-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
Call Trace:
__dump_stack lib/dump_stack.c:17 [inline]
dump_stack+0x13e/0x194 lib/dump_stack.c:58
panic+0x1f9/0x42d kernel/panic.c:183
__warn.cold+0x2f/0x30 kernel/panic.c:547
report_bug+0x20a/0x248 lib/bug.c:186
fixup_bug arch/x86/kernel/traps.c:177 [inline]
fixup_bug arch/x86/kernel/traps.c:172 [inline]
do_error_trap+0x195/0x2d0 arch/x86/kernel/traps.c:295
invalid_op+0x1b/0x40 arch/x86/entry/entry_64.S:963
RIP: 0010:debug_print_object.cold+0xa7/0xdb lib/debugobjects.c:287
RSP: 0018:ffff88804b50fb10 EFLAGS: 00010086
RAX: 000000000000005e RBX: 0000000000000003 RCX: 0000000000000000
RDX: 0000000000028629 RSI: ffffffff81491370 RDI: ffffed10096a1f58
RBP: ffffffff86abba60 R08: 000000000000005e R09: 0000000000000000
R10: fffffbfff14a8cd9 R11: ffff8880991a8600 R12: ffffffff85a89100
R13: 0000000000000000 R14: ffffffff8a760c88 R15: ffff888096350850
__debug_check_no_obj_freed lib/debugobjects.c:747 [inline]
debug_check_no_obj_freed+0x3cd/0x6e4 lib/debugobjects.c:776
kfree+0xbb/0x260 mm/slab.c:3814
rfcomm_dlc_put include/net/bluetooth/rfcomm.h:258 [inline]
__rfcomm_create_dev net/bluetooth/rfcomm/tty.c:417 [inline]
rfcomm_create_dev net/bluetooth/rfcomm/tty.c:486 [inline]
rfcomm_dev_ioctl+0x151f/0x1810 net/bluetooth/rfcomm/tty.c:588
rfcomm_sock_ioctl+0x7d/0xa0 net/bluetooth/rfcomm/sock.c:902
sock_do_ioctl+0x5f/0xa0 net/socket.c:974
sock_ioctl+0x28d/0x450 net/socket.c:1071
vfs_ioctl fs/ioctl.c:46 [inline]
file_ioctl fs/ioctl.c:500 [inline]
do_vfs_ioctl+0x75a/0xfe0 fs/ioctl.c:684
SYSC_ioctl fs/ioctl.c:701 [inline]
SyS_ioctl+0x7f/0xb0 fs/ioctl.c:692
do_syscall_64+0x1d5/0x640 arch/x86/entry/common.c:292
entry_SYSCALL_64_after_hwframe+0x42/0xb7
RIP: 0033:0x45c849
RSP: 002b:00007f79586a9c78 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 00007f79586aa6d4 RCX: 000000000045c849
RDX: 0000000020000100 RSI: 00000000400452c8 RDI: 0000000000000004
RBP: 000000000076bf00 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 00000000ffffffff
R13: 0000000000000316 R14: 00000000004c57dd R15: 000000000076bf0c

======================================================


---
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 23, 2020, 3:17:15 PM3/23/20
to syzkaller...@googlegroups.com
syzbot has found a reproducer for 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=11e8dce5e00000
kernel config: https://syzkaller.appspot.com/x/.config?x=664dd71881ab2b2d
dashboard link: https://syzkaller.appspot.com/bug?extid=ed209d00d1a00ff450e8
compiler: gcc (GCC) 9.0.0 20181231 (experimental)
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=16662b19e00000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=138ed441e00000

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

audit: type=1400 audit(1584990865.292:36): avc: denied { map } for pid=7401 comm="syz-executor812" path="/root/syz-executor812287922" dev="sda1" ino=16483 scontext=unconfined_u:system_r:insmod_t:s0-s0:c0.c1023 tcontext=unconfined_u:object_r:user_home_t:s0 tclass=file permissive=1
ODEBUG: free active (active state 0) object type: timer_list hint: __write_once_size include/linux/compiler.h:210 [inline]
ODEBUG: free active (active state 0) object type: timer_list hint: __list_add include/linux/list.h:66 [inline]
ODEBUG: free active (active state 0) object type: timer_list hint: list_add include/linux/list.h:79 [inline]
ODEBUG: free active (active state 0) object type: timer_list hint: rfcomm_dlc_timeout+0x0/0x60 net/bluetooth/rfcomm/core.c:337
------------[ cut here ]------------
WARNING: CPU: 0 PID: 7404 at lib/debugobjects.c:287 debug_print_object.cold+0xa7/0xdb lib/debugobjects.c:287
Kernel panic - not syncing: panic_on_warn set ...

CPU: 0 PID: 7404 Comm: syz-executor812 Not tainted 4.14.174-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
Call Trace:
__dump_stack lib/dump_stack.c:17 [inline]
dump_stack+0x13e/0x194 lib/dump_stack.c:58
panic+0x1f9/0x42d kernel/panic.c:183
__warn.cold+0x2f/0x30 kernel/panic.c:547
report_bug+0x20a/0x248 lib/bug.c:186
fixup_bug arch/x86/kernel/traps.c:177 [inline]
fixup_bug arch/x86/kernel/traps.c:172 [inline]
do_error_trap+0x195/0x2d0 arch/x86/kernel/traps.c:295
invalid_op+0x1b/0x40 arch/x86/entry/entry_64.S:963
RIP: 0010:debug_print_object.cold+0xa7/0xdb lib/debugobjects.c:287
RSP: 0018:ffff88809157fb10 EFLAGS: 00010086
RAX: 000000000000005e RBX: 0000000000000003 RCX: 0000000000000000
RDX: 0000000000000000 RSI: ffffffff86ac07e0 RDI: ffffed10122aff58
RBP: ffffffff86abba60 R08: 000000000000005e R09: 0000000000000000
R10: fffffbfff14a8cd9 R11: ffff8880827e4600 R12: ffffffff85a89100
R13: 0000000000000000 R14: ffffffff8a72d088 R15: ffff88808fad9c40
__debug_check_no_obj_freed lib/debugobjects.c:747 [inline]
debug_check_no_obj_freed+0x3cd/0x6e4 lib/debugobjects.c:776
kfree+0xbb/0x260 mm/slab.c:3814
rfcomm_dlc_put include/net/bluetooth/rfcomm.h:258 [inline]
__rfcomm_create_dev net/bluetooth/rfcomm/tty.c:417 [inline]
rfcomm_create_dev net/bluetooth/rfcomm/tty.c:486 [inline]
rfcomm_dev_ioctl+0x151f/0x1810 net/bluetooth/rfcomm/tty.c:588
rfcomm_sock_ioctl+0x7d/0xa0 net/bluetooth/rfcomm/sock.c:902
sock_do_ioctl+0x5f/0xa0 net/socket.c:974
sock_ioctl+0x28d/0x450 net/socket.c:1071
vfs_ioctl fs/ioctl.c:46 [inline]
file_ioctl fs/ioctl.c:500 [inline]
do_vfs_ioctl+0x75a/0xfe0 fs/ioctl.c:684
SYSC_ioctl fs/ioctl.c:701 [inline]
SyS_ioctl+0x7f/0xb0 fs/ioctl.c:692
do_syscall_64+0x1d5/0x640 arch/x86/entry/common.c:292
entry_SYSCALL_64_after_hwframe+0x42/0xb7
RIP: 0033:0x441309
RSP: 002b:00007ffff0f7aa08 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 0000000000441309
RDX: 0000000020000100 RSI: 00000000400452c8 RDI: 0000000000000005
RBP: 000000000000bab9 R08: 00000000004002c8 R09: 00000000004002c8
R10: 00000000004002c8 R11: 0000000000000246 R12: 0000000000402130
R13: 00000000004021c0 R14: 0000000000000000 R15: 0000000000000000

======================================================

syzbot

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

syzbot found the following crash on:

HEAD commit: 54b4fa6d Linux 4.19.113
git tree: linux-4.19.y
console output: https://syzkaller.appspot.com/x/log.txt?x=10f62e83e00000
kernel config: https://syzkaller.appspot.com/x/.config?x=7b1a0bc5526ebc49
dashboard link: https://syzkaller.appspot.com/bug?extid=0b14a6cccc936e2b7915
compiler: gcc (GCC) 9.0.0 20181231 (experimental)
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1556ba33e00000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1609d5a3e00000

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

audit: type=1400 audit(1585388686.892:36): avc: denied { map } for pid=8244 comm="syz-executor838" path="/root/syz-executor838454775" dev="sda1" ino=16483 scontext=unconfined_u:system_r:insmod_t:s0-s0:c0.c1023 tcontext=unconfined_u:object_r:user_home_t:s0 tclass=file permissive=1
------------[ cut here ]------------
ODEBUG: free active (active state 0) object type: timer_list hint: rfcomm_dlc_timeout+0x0/0x70 include/linux/compiler.h:220
WARNING: CPU: 1 PID: 8247 at lib/debugobjects.c:325 debug_print_object+0x160/0x250 lib/debugobjects.c:325
Kernel panic - not syncing: panic_on_warn set ...

CPU: 1 PID: 8247 Comm: syz-executor838 Not tainted 4.19.113-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+0x188/0x20d lib/dump_stack.c:118
panic+0x26a/0x50e kernel/panic.c:186
__warn.cold+0x20/0x46 kernel/panic.c:541
report_bug+0x262/0x2a0 lib/bug.c:186
fixup_bug arch/x86/kernel/traps.c:178 [inline]
fixup_bug arch/x86/kernel/traps.c:173 [inline]
do_error_trap+0x1d7/0x310 arch/x86/kernel/traps.c:296
invalid_op+0x14/0x20 arch/x86/entry/entry_64.S:1037
RIP: 0010:debug_print_object+0x160/0x250 lib/debugobjects.c:325
Code: dd 60 0b ab 87 48 89 fa 48 c1 ea 03 80 3c 02 00 0f 85 bf 00 00 00 48 8b 14 dd 60 0b ab 87 48 c7 c7 a0 00 ab 87 e8 0b 65 e6 fd <0f> 0b 83 05 13 11 37 06 01 48 83 c4 20 5b 5d 41 5c 41 5d c3 48 89
RSP: 0018:ffff88809f757920 EFLAGS: 00010086
RAX: 0000000000000000 RBX: 0000000000000003 RCX: 0000000000000000
RDX: 0000000000000000 RSI: ffffffff8152d3a1 RDI: ffffed1013eeaf16
RBP: 0000000000000001 R08: ffff888090af2540 R09: ffffed1015ce3ee3
R10: ffffed1015ce3ee2 R11: ffff8880ae71f717 R12: ffffffff88b9faa0
R13: ffffffff81581ee0 R14: ffffffff8b8c98c8 R15: ffff88808b5bd3a8
__debug_check_no_obj_freed lib/debugobjects.c:785 [inline]
debug_check_no_obj_freed+0x2a3/0x42e lib/debugobjects.c:817
kfree+0xbb/0x220 mm/slab.c:3821
rfcomm_dlc_put include/net/bluetooth/rfcomm.h:258 [inline]
__rfcomm_create_dev net/bluetooth/rfcomm/tty.c:417 [inline]
rfcomm_create_dev net/bluetooth/rfcomm/tty.c:486 [inline]
rfcomm_dev_ioctl+0x1827/0x1b20 net/bluetooth/rfcomm/tty.c:588
rfcomm_sock_ioctl+0x86/0xb0 net/bluetooth/rfcomm/sock.c:902
sock_do_ioctl+0xd8/0x2f0 net/socket.c:950
sock_ioctl+0x325/0x610 net/socket.c:1074
vfs_ioctl fs/ioctl.c:46 [inline]
file_ioctl fs/ioctl.c:501 [inline]
do_vfs_ioctl+0xcda/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:0x441309
Code: e8 fc ab 02 00 48 83 c4 18 c3 0f 1f 80 00 00 00 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 0f 83 9b 09 fc ff c3 66 2e 0f 1f 84 00 00 00 00
RSP: 002b:00007fff89399938 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 0000000000441309
RDX: 0000000020000100 RSI: 00000000400452c8 RDI: 0000000000000005
RBP: 0000000000010cb7 R08: 00000000004002c8 R09: 00000000004002c8
R10: 00000000004002c8 R11: 0000000000000246 R12: 0000000000402130
R13: 00000000004021c0 R14: 0000000000000000 R15: 0000000000000000

======================================================


---
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 can test patches for this bug, for details see:
https://goo.gl/tpsmEJ#testing-patches

syzbot

unread,
Apr 22, 2020, 5:25:04 PM4/22/20
to syzkaller...@googlegroups.com
syzbot suspects this bug was fixed by commit:

commit 0da9c032adbb6f83cc7f548c5155d26c64f44d63
Author: Qiujun Huang <hqja...@gmail.com>
Date: Sun Mar 8 09:45:27 2020 +0000

Bluetooth: RFCOMM: fix ODEBUG bug in rfcomm_dev_ioctl

bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=140ad2cfe00000
start commit: 01364dad Linux 4.14.174
git tree: linux-4.14.y
If the result looks correct, please mark the bug fixed by replying with:

#syz fix: Bluetooth: RFCOMM: fix ODEBUG bug in rfcomm_dev_ioctl

For information about bisection process see: https://goo.gl/tpsmEJ#bisection

syzbot

unread,
Apr 27, 2020, 9:04:04 AM4/27/20
to syzkaller...@googlegroups.com
syzbot suspects this bug was fixed by commit:

commit 78a4ad28608a530b5bd85da60307d61133e68040
Author: Qiujun Huang <hqja...@gmail.com>
Date: Sun Mar 8 09:45:27 2020 +0000

Bluetooth: RFCOMM: fix ODEBUG bug in rfcomm_dev_ioctl

bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=12fba9a0100000
start commit: 54b4fa6d Linux 4.19.113
git tree: linux-4.19.y
Reply all
Reply to author
Forward
0 new messages