general protection fault in l2cap_chan_timeout (2)
8 views
Skip to first unread message
syzbot
Jun 23, 2021, 5:07:25 PM6/23/21
to syzkaller...@googlegroups.com
Hello,
syzbot found the following issue on:
HEAD commit: eb575cd5 Linux 4.19.195
git tree: linux-4.19.y
console output: https://syzkaller.appspot.com/x/log.txt?x=126926a0300000
kernel config: https://syzkaller.appspot.com/x/.config?x=5506475cccaff975
dashboard link: https://syzkaller.appspot.com/bug?extid=134361f2dab7d2d9f8a2
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+134361...@syzkaller.appspotmail.com
*** Guest State ***
CR0: actual=0x0000000000000030, shadow=0x0000000060000010, gh_mask=fffffffffffffff7
CR4: actual=0x0000000000002040, shadow=0x0000000000000000, gh_mask=ffffffffffffe871
kasan: CONFIG_KASAN_INLINE enabled
kasan: GPF could be caused by NULL-ptr deref or user memory access
general protection fault: 0000 [#1] PREEMPT SMP KASAN
CPU: 0 PID: 14 Comm: kworker/0:1 Not tainted 4.19.195-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
Workqueue: events l2cap_chan_timeout
RIP: 0010:trace_event_get_offsets_lock_acquire include/trace/events/lock.h:13 [inline]
RIP: 0010:perf_trace_lock_acquire+0x9d/0x530 include/trace/events/lock.h:13
Code: 04 f1 f1 04 f2 c7 40 08 00 f3 f3 f3 65 48 8b 04 25 28 00 00 00 48 89 45 d0 31 c0 48 8d 46 18 48 89 85 40 ff ff ff 48 c1 e8 03 <80> 3c 10 00 0f 85 4f 03 00 00 49 8b 7d 18 48 c7 c0 80 14 6a 88 48
RSP: 0018:ffff8880b5a97a38 EFLAGS: 00010006
RAX: 0000000000000056 RBX: ffff8880aac15828 RCX: 0000000000000000
RDX: dffffc0000000000 RSI: 0000000000000298 RDI: ffffffff89f6d360
RBP: ffff8880b5a97b20 R08: 0000000000000000 R09: 0000000000000001
R10: 0000000000000001 R11: 0000000000074071 R12: ffffffff89f6d360
R13: 0000000000000298 R14: 0000000000000000 R15: ffff8880b5a97af8
FS: 0000000000000000(0000) GS:ffff8880ba000000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00005631eb987238 CR3: 00000000a19e9000 CR4: 00000000001426f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
trace_lock_acquire include/trace/events/lock.h:13 [inline]
lock_acquire+0x298/0x3c0 kernel/locking/lockdep.c:3907
__mutex_lock_common kernel/locking/mutex.c:938 [inline]
__mutex_lock+0xd7/0x1200 kernel/locking/mutex.c:1083
l2cap_chan_timeout+0x69/0x2f0 net/bluetooth/l2cap_core.c:416
process_one_work+0x864/0x1570 kernel/workqueue.c:2153
worker_thread+0x64c/0x1130 kernel/workqueue.c:2296
kthread+0x33f/0x460 kernel/kthread.c:259
ret_from_fork+0x24/0x30 arch/x86/entry/entry_64.S:415
Modules linked in:
---[ end trace d045a62c167ce1ec ]---
RIP: 0010:trace_event_get_offsets_lock_acquire include/trace/events/lock.h:13 [inline]
RIP: 0010:perf_trace_lock_acquire+0x9d/0x530 include/trace/events/lock.h:13
Code: 04 f1 f1 04 f2 c7 40 08 00 f3 f3 f3 65 48 8b 04 25 28 00 00 00 48 89 45 d0 31 c0 48 8d 46 18 48 89 85 40 ff ff ff 48 c1 e8 03 <80> 3c 10 00 0f 85 4f 03 00 00 49 8b 7d 18 48 c7 c0 80 14 6a 88 48
RSP: 0018:ffff8880b5a97a38 EFLAGS: 00010006
RAX: 0000000000000056 RBX: ffff8880aac15828 RCX: 0000000000000000
RDX: dffffc0000000000 RSI: 0000000000000298 RDI: ffffffff89f6d360
RBP: ffff8880b5a97b20 R08: 0000000000000000 R09: 0000000000000001
R10: 0000000000000001 R11: 0000000000074071 R12: ffffffff89f6d360
R13: 0000000000000298 R14: 0000000000000000 R15: ffff8880b5a97af8
FS: 0000000000000000(0000) GS:ffff8880ba000000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00005631eb987238 CR3: 00000000a19e9000 CR4: 00000000001426f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
---
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 found the following issue on:
HEAD commit: eb575cd5 Linux 4.19.195
git tree: linux-4.19.y
console output: https://syzkaller.appspot.com/x/log.txt?x=126926a0300000
kernel config: https://syzkaller.appspot.com/x/.config?x=5506475cccaff975
dashboard link: https://syzkaller.appspot.com/bug?extid=134361f2dab7d2d9f8a2
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+134361...@syzkaller.appspotmail.com
*** Guest State ***
CR0: actual=0x0000000000000030, shadow=0x0000000060000010, gh_mask=fffffffffffffff7
CR4: actual=0x0000000000002040, shadow=0x0000000000000000, gh_mask=ffffffffffffe871
kasan: CONFIG_KASAN_INLINE enabled
kasan: GPF could be caused by NULL-ptr deref or user memory access
general protection fault: 0000 [#1] PREEMPT SMP KASAN
CPU: 0 PID: 14 Comm: kworker/0:1 Not tainted 4.19.195-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
Workqueue: events l2cap_chan_timeout
RIP: 0010:trace_event_get_offsets_lock_acquire include/trace/events/lock.h:13 [inline]
RIP: 0010:perf_trace_lock_acquire+0x9d/0x530 include/trace/events/lock.h:13
Code: 04 f1 f1 04 f2 c7 40 08 00 f3 f3 f3 65 48 8b 04 25 28 00 00 00 48 89 45 d0 31 c0 48 8d 46 18 48 89 85 40 ff ff ff 48 c1 e8 03 <80> 3c 10 00 0f 85 4f 03 00 00 49 8b 7d 18 48 c7 c0 80 14 6a 88 48
RSP: 0018:ffff8880b5a97a38 EFLAGS: 00010006
RAX: 0000000000000056 RBX: ffff8880aac15828 RCX: 0000000000000000
RDX: dffffc0000000000 RSI: 0000000000000298 RDI: ffffffff89f6d360
RBP: ffff8880b5a97b20 R08: 0000000000000000 R09: 0000000000000001
R10: 0000000000000001 R11: 0000000000074071 R12: ffffffff89f6d360
R13: 0000000000000298 R14: 0000000000000000 R15: ffff8880b5a97af8
FS: 0000000000000000(0000) GS:ffff8880ba000000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00005631eb987238 CR3: 00000000a19e9000 CR4: 00000000001426f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
trace_lock_acquire include/trace/events/lock.h:13 [inline]
lock_acquire+0x298/0x3c0 kernel/locking/lockdep.c:3907
__mutex_lock_common kernel/locking/mutex.c:938 [inline]
__mutex_lock+0xd7/0x1200 kernel/locking/mutex.c:1083
l2cap_chan_timeout+0x69/0x2f0 net/bluetooth/l2cap_core.c:416
process_one_work+0x864/0x1570 kernel/workqueue.c:2153
worker_thread+0x64c/0x1130 kernel/workqueue.c:2296
kthread+0x33f/0x460 kernel/kthread.c:259
ret_from_fork+0x24/0x30 arch/x86/entry/entry_64.S:415
Modules linked in:
---[ end trace d045a62c167ce1ec ]---
RIP: 0010:trace_event_get_offsets_lock_acquire include/trace/events/lock.h:13 [inline]
RIP: 0010:perf_trace_lock_acquire+0x9d/0x530 include/trace/events/lock.h:13
Code: 04 f1 f1 04 f2 c7 40 08 00 f3 f3 f3 65 48 8b 04 25 28 00 00 00 48 89 45 d0 31 c0 48 8d 46 18 48 89 85 40 ff ff ff 48 c1 e8 03 <80> 3c 10 00 0f 85 4f 03 00 00 49 8b 7d 18 48 c7 c0 80 14 6a 88 48
RSP: 0018:ffff8880b5a97a38 EFLAGS: 00010006
RAX: 0000000000000056 RBX: ffff8880aac15828 RCX: 0000000000000000
RDX: dffffc0000000000 RSI: 0000000000000298 RDI: ffffffff89f6d360
RBP: ffff8880b5a97b20 R08: 0000000000000000 R09: 0000000000000001
R10: 0000000000000001 R11: 0000000000074071 R12: ffffffff89f6d360
R13: 0000000000000298 R14: 0000000000000000 R15: ffff8880b5a97af8
FS: 0000000000000000(0000) GS:ffff8880ba000000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00005631eb987238 CR3: 00000000a19e9000 CR4: 00000000001426f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
---
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
Sep 23, 2021, 6:10:18 PM9/23/21
to syzkaller...@googlegroups.com
syzbot has found a reproducer for the following issue on:
HEAD commit: 2950c9c5e0df Linux 4.19.207
git tree: linux-4.19.y
console output: https://syzkaller.appspot.com/x/log.txt?x=1129740b300000
kernel config: https://syzkaller.appspot.com/x/.config?x=8273060cfa230984
dashboard link: https://syzkaller.appspot.com/bug?extid=134361f2dab7d2d9f8a2
compiler: gcc version 10.2.1 20210110 (Debian 10.2.1-6)
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=135304d3300000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=17db609d300000
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+134361...@syzkaller.appspotmail.com
Code: 2b 29 00 00 48 81 c4 98 01 00 00 44 89 f8 5b 5d 41 5c 41 5d 41 5e 41 5f c3 48 b8 00 00 00 00 00 fc ff df 4c 89 f2 48 c1 ea 03 <80> 3c 02 00 0f 85 b3 2a 00 00 49 81 3e 20 f2 66 8c 0f 84 65 ff ff
RSP: 0018:ffff8880af37f958 EFLAGS: 00010006
RAX: dffffc0000000000 RBX: 0000000000000000 RCX: 0000000000000000
RDX: 0000000000000053 RSI: 0000000000000000 RDI: 0000000000000001
RBP: 0000000000000000 R08: 0000000000000000 R09: 0000000000000001
R10: 0000000000000001 R11: 0000000000074071 R12: 0000000000000000
R13: ffff8880b3b7e080 R14: 0000000000000298 R15: 0000000000000001
__mutex_lock_common kernel/locking/mutex.c:937 [inline]
__mutex_lock+0xd7/0x1190 kernel/locking/mutex.c:1078
RIP: 0010:__lock_acquire+0x1eb/0x3ff0 kernel/locking/lockdep.c:3295
Code: 2b 29 00 00 48 81 c4 98 01 00 00 44 89 f8 5b 5d 41 5c 41 5d 41 5e 41 5f c3 48 b8 00 00 00 00 00 fc ff df 4c 89 f2 48 c1 ea 03 <80> 3c 02 00 0f 85 b3 2a 00 00 49 81 3e 20 f2 66 8c 0f 84 65 ff ff
RSP: 0018:ffff8880af37f958 EFLAGS: 00010006
RAX: dffffc0000000000 RBX: 0000000000000000 RCX: 0000000000000000
RDX: 0000000000000053 RSI: 0000000000000000 RDI: 0000000000000001
RBP: 0000000000000000 R08: 0000000000000000 R09: 0000000000000001
R10: 0000000000000001 R11: 0000000000074071 R12: 0000000000000000
R13: ffff8880b3b7e080 R14: 0000000000000298 R15: 0000000000000001
Code disassembly (best guess):
0: 2b 29 sub (%rcx),%ebp
2: 00 00 add %al,(%rax)
4: 48 81 c4 98 01 00 00 add $0x198,%rsp
b: 44 89 f8 mov %r15d,%eax
e: 5b pop %rbx
f: 5d pop %rbp
10: 41 5c pop %r12
12: 41 5d pop %r13
14: 41 5e pop %r14
16: 41 5f pop %r15
18: c3 retq
19: 48 b8 00 00 00 00 00 movabs $0xdffffc0000000000,%rax
20: fc ff df
23: 4c 89 f2 mov %r14,%rdx
26: 48 c1 ea 03 shr $0x3,%rdx
* 2a: 80 3c 02 00 cmpb $0x0,(%rdx,%rax,1) <-- trapping instruction
2e: 0f 85 b3 2a 00 00 jne 0x2ae7
34: 49 81 3e 20 f2 66 8c cmpq $0xffffffff8c66f220,(%r14)
3b: 0f .byte 0xf
3c: 84 65 ff test %ah,-0x1(%rbp)
3f: ff .byte 0xff
HEAD commit: 2950c9c5e0df Linux 4.19.207
git tree: linux-4.19.y
console output: https://syzkaller.appspot.com/x/log.txt?x=1129740b300000
kernel config: https://syzkaller.appspot.com/x/.config?x=8273060cfa230984
dashboard link: https://syzkaller.appspot.com/bug?extid=134361f2dab7d2d9f8a2
compiler: gcc version 10.2.1 20210110 (Debian 10.2.1-6)
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=135304d3300000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=17db609d300000
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+134361...@syzkaller.appspotmail.com
kasan: CONFIG_KASAN_INLINE enabled
kasan: GPF could be caused by NULL-ptr deref or user memory access
general protection fault: 0000 [#1] PREEMPT SMP KASAN
CPU: 0 PID: 8170 Comm: kworker/0:0 Not tainted 4.19.207-syzkaller #0
kasan: GPF could be caused by NULL-ptr deref or user memory access
general protection fault: 0000 [#1] PREEMPT SMP KASAN
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
Workqueue: events l2cap_chan_timeout
RIP: 0010:__lock_acquire+0x1eb/0x3ff0 kernel/locking/lockdep.c:3295
Workqueue: events l2cap_chan_timeout
Code: 2b 29 00 00 48 81 c4 98 01 00 00 44 89 f8 5b 5d 41 5c 41 5d 41 5e 41 5f c3 48 b8 00 00 00 00 00 fc ff df 4c 89 f2 48 c1 ea 03 <80> 3c 02 00 0f 85 b3 2a 00 00 49 81 3e 20 f2 66 8c 0f 84 65 ff ff
RSP: 0018:ffff8880af37f958 EFLAGS: 00010006
RAX: dffffc0000000000 RBX: 0000000000000000 RCX: 0000000000000000
RDX: 0000000000000053 RSI: 0000000000000000 RDI: 0000000000000001
RBP: 0000000000000000 R08: 0000000000000000 R09: 0000000000000001
R10: 0000000000000001 R11: 0000000000074071 R12: 0000000000000000
R13: ffff8880b3b7e080 R14: 0000000000000298 R15: 0000000000000001
FS: 0000000000000000(0000) GS:ffff8880ba000000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fc374dbc718 CR3: 00000000928c0000 CR4: 00000000001406f0
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
lock_acquire+0x170/0x3c0 kernel/locking/lockdep.c:3908
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
__mutex_lock_common kernel/locking/mutex.c:937 [inline]
__mutex_lock+0xd7/0x1190 kernel/locking/mutex.c:1078
l2cap_chan_timeout+0x69/0x2f0 net/bluetooth/l2cap_core.c:416
process_one_work+0x864/0x1570 kernel/workqueue.c:2153
worker_thread+0x64c/0x1130 kernel/workqueue.c:2296
kthread+0x33f/0x460 kernel/kthread.c:259
ret_from_fork+0x24/0x30 arch/x86/entry/entry_64.S:415
Modules linked in:
---[ end trace 92fca598f788abb7 ]---
process_one_work+0x864/0x1570 kernel/workqueue.c:2153
worker_thread+0x64c/0x1130 kernel/workqueue.c:2296
kthread+0x33f/0x460 kernel/kthread.c:259
ret_from_fork+0x24/0x30 arch/x86/entry/entry_64.S:415
Modules linked in:
RIP: 0010:__lock_acquire+0x1eb/0x3ff0 kernel/locking/lockdep.c:3295
Code: 2b 29 00 00 48 81 c4 98 01 00 00 44 89 f8 5b 5d 41 5c 41 5d 41 5e 41 5f c3 48 b8 00 00 00 00 00 fc ff df 4c 89 f2 48 c1 ea 03 <80> 3c 02 00 0f 85 b3 2a 00 00 49 81 3e 20 f2 66 8c 0f 84 65 ff ff
RSP: 0018:ffff8880af37f958 EFLAGS: 00010006
RAX: dffffc0000000000 RBX: 0000000000000000 RCX: 0000000000000000
RDX: 0000000000000053 RSI: 0000000000000000 RDI: 0000000000000001
RBP: 0000000000000000 R08: 0000000000000000 R09: 0000000000000001
R10: 0000000000000001 R11: 0000000000074071 R12: 0000000000000000
R13: ffff8880b3b7e080 R14: 0000000000000298 R15: 0000000000000001
FS: 0000000000000000(0000) GS:ffff8880ba000000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fc374dbc718 CR3: 00000000928c0000 CR4: 00000000001406f0
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
----------------
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Code disassembly (best guess):
0: 2b 29 sub (%rcx),%ebp
2: 00 00 add %al,(%rax)
4: 48 81 c4 98 01 00 00 add $0x198,%rsp
b: 44 89 f8 mov %r15d,%eax
e: 5b pop %rbx
f: 5d pop %rbp
10: 41 5c pop %r12
12: 41 5d pop %r13
14: 41 5e pop %r14
16: 41 5f pop %r15
18: c3 retq
19: 48 b8 00 00 00 00 00 movabs $0xdffffc0000000000,%rax
20: fc ff df
23: 4c 89 f2 mov %r14,%rdx
26: 48 c1 ea 03 shr $0x3,%rdx
* 2a: 80 3c 02 00 cmpb $0x0,(%rdx,%rax,1) <-- trapping instruction
2e: 0f 85 b3 2a 00 00 jne 0x2ae7
34: 49 81 3e 20 f2 66 8c cmpq $0xffffffff8c66f220,(%r14)
3b: 0f .byte 0xf
3c: 84 65 ff test %ah,-0x1(%rbp)
3f: ff .byte 0xff
Reply all
Reply to author
Forward
0 new messages