general protection fault in hci_phy_link_complete_evt
9 views
Skip to first unread message
syzbot
Aug 2, 2020, 4:56:22 AM8/2/20
to syzkaller...@googlegroups.com
Hello,
syzbot found 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=16c0d9ea900000
kernel config: https://syzkaller.appspot.com/x/.config?x=881f1aee9620bf9f
dashboard link: https://syzkaller.appspot.com/bug?extid=c95f9a03e069d5406cfa
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:
Reported-by: syzbot+c95f9a...@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
Modules linked in:
CPU: 1 PID: 8497 Comm: kworker/u5:2 Not tainted 4.14.191-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
Workqueue: hci1 hci_rx_work
task: ffff8880668f0200 task.stack: ffff888064018000
RIP: 0010:hci_phy_link_complete_evt.isra.0+0x1f3/0x6c0 net/bluetooth/hci_event.c:4360
RSP: 0018:ffff88806401fad0 EFLAGS: 00010202
RAX: dffffc0000000000 RBX: 0000000000000000 RCX: 1ffff1100cd1e160
RDX: 0000000000000002 RSI: 0000000000000004 RDI: 0000000000000010
RBP: ffff88809cbfc440 R08: 0000000000000000 R09: 0000000000000003
R10: 0000000000000000 R11: ffff8880668f0200 R12: ffff888060029ca8
R13: 00000000000000c8 R14: ffff88805fe15d4b R15: ffff888060028d50
FS: 0000000000000000(0000) GS:ffff8880aeb00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000000000078c000 CR3: 00000000a4c2e000 CR4: 00000000001406e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
hci_event_packet+0x2592/0x7c7a net/bluetooth/hci_event.c:5429
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
Code: fa 48 c1 ea 03 80 3c 02 00 0f 85 dd 04 00 00 48 8b 9d 40 08 00 00 48 b8 00 00 00 00 00 fc ff df 48 8d 7b 10 48 89 fa 48 c1 ea 03 <80> 3c 02 00 0f 85 a0 04 00 00 48 b8 00 00 00 00 00 fc ff df 48
RIP: hci_phy_link_complete_evt.isra.0+0x1f3/0x6c0 net/bluetooth/hci_event.c:4360 RSP: ffff88806401fad0
---[ end trace 8210b03616886dce ]---
---
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: 7f2c5eb4 Linux 4.14.191
git tree: linux-4.14.y
console output: https://syzkaller.appspot.com/x/log.txt?x=16c0d9ea900000
kernel config: https://syzkaller.appspot.com/x/.config?x=881f1aee9620bf9f
dashboard link: https://syzkaller.appspot.com/bug?extid=c95f9a03e069d5406cfa
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:
Reported-by: syzbot+c95f9a...@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
Modules linked in:
CPU: 1 PID: 8497 Comm: kworker/u5:2 Not tainted 4.14.191-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
Workqueue: hci1 hci_rx_work
task: ffff8880668f0200 task.stack: ffff888064018000
RIP: 0010:hci_phy_link_complete_evt.isra.0+0x1f3/0x6c0 net/bluetooth/hci_event.c:4360
RSP: 0018:ffff88806401fad0 EFLAGS: 00010202
RAX: dffffc0000000000 RBX: 0000000000000000 RCX: 1ffff1100cd1e160
RDX: 0000000000000002 RSI: 0000000000000004 RDI: 0000000000000010
RBP: ffff88809cbfc440 R08: 0000000000000000 R09: 0000000000000003
R10: 0000000000000000 R11: ffff8880668f0200 R12: ffff888060029ca8
R13: 00000000000000c8 R14: ffff88805fe15d4b R15: ffff888060028d50
FS: 0000000000000000(0000) GS:ffff8880aeb00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000000000078c000 CR3: 00000000a4c2e000 CR4: 00000000001406e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
hci_event_packet+0x2592/0x7c7a net/bluetooth/hci_event.c:5429
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
Code: fa 48 c1 ea 03 80 3c 02 00 0f 85 dd 04 00 00 48 8b 9d 40 08 00 00 48 b8 00 00 00 00 00 fc ff df 48 8d 7b 10 48 89 fa 48 c1 ea 03 <80> 3c 02 00 0f 85 a0 04 00 00 48 b8 00 00 00 00 00 fc ff df 48
RIP: hci_phy_link_complete_evt.isra.0+0x1f3/0x6c0 net/bluetooth/hci_event.c:4360 RSP: ffff88806401fad0
---[ end trace 8210b03616886dce ]---
---
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
Aug 2, 2020, 5:00:19 AM8/2/20
to syzkaller...@googlegroups.com
Hello,
syzbot found the following issue on:
HEAD commit: 13af6c74 Linux 4.19.136
syzbot found the following issue on:
git tree: linux-4.19.y
console output: https://syzkaller.appspot.com/x/log.txt?x=10689bca900000
kernel config: https://syzkaller.appspot.com/x/.config?x=5b7578d3b5457a49
dashboard link: https://syzkaller.appspot.com/bug?extid=477d30719250034f2009
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:
Reported-by: syzbot+477d30...@syzkaller.appspotmail.com
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:
IPv6: ADDRCONF(NETDEV_CHANGE): veth1_virt_wifi: link becomes ready
kasan: CONFIG_KASAN_INLINE enabled
IPv6: ADDRCONF(NETDEV_CHANGE): veth0_virt_wifi: link becomes ready
kasan: GPF could be caused by NULL-ptr deref or user memory access
IPv6: ADDRCONF(NETDEV_UP): veth1_macvtap: link is not ready
general protection fault: 0000 [#1] PREEMPT SMP KASAN
CPU: 0 PID: 1228 Comm: kworker/u5:0 Not tainted 4.19.136-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
Workqueue: hci0 hci_rx_work
RIP: 0010:hci_phy_link_complete_evt.isra.0+0x24a/0x7a0 net/bluetooth/hci_event.c:4682
Code: 48 c1 ea 03 80 3c 02 00 0f 85 60 05 00 00 48 8b 9d 28 08 00 00 48 b8 00 00 00 00 00 fc ff df 48 8d 7b 10 48 89 fa 48 c1 ea 03 <80> 3c 02 00 0f 85 23 05 00 00 48 b8 00 00 00 00 00 fc ff df 48 8b
RSP: 0018:ffff8880a7617a78 EFLAGS: 00010202
RAX: dffffc0000000000 RBX: 0000000000000000 RCX: ffffffff867c041f
RDX: 0000000000000002 RSI: ffffffff867c042c RDI: 0000000000000010
RBP: ffff8880536c6500 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000001 R11: 0000000000000000 R12: dffffc0000000000
R13: ffff8880535aee00 R14: 00000000000000c8 R15: ffff8880535aded0
FS: 0000000000000000(0000) GS:ffff8880ae600000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f3407845000 CR3: 00000000911c4000 CR4: 00000000001406f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
hci_event_packet+0x1973/0x858f net/bluetooth/hci_event.c:5898
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
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
Modules linked in:
---[ end trace caa5fd8d66c85959 ]---
RIP: 0010:hci_phy_link_complete_evt.isra.0+0x24a/0x7a0 net/bluetooth/hci_event.c:4682
Code: 48 c1 ea 03 80 3c 02 00 0f 85 60 05 00 00 48 8b 9d 28 08 00 00 48 b8 00 00 00 00 00 fc ff df 48 8d 7b 10 48 89 fa 48 c1 ea 03 <80> 3c 02 00 0f 85 23 05 00 00 48 b8 00 00 00 00 00 fc ff df 48 8b
RSP: 0018:ffff8880a7617a78 EFLAGS: 00010202
RAX: dffffc0000000000 RBX: 0000000000000000 RCX: ffffffff867c041f
RDX: 0000000000000002 RSI: ffffffff867c042c RDI: 0000000000000010
RBP: ffff8880536c6500 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000001 R11: 0000000000000000 R12: dffffc0000000000
R13: ffff8880535aee00 R14: 00000000000000c8 R15: ffff8880535aded0
FS: 0000000000000000(0000) GS:ffff8880ae700000(0000) knlGS:0000000000000000
IPv6: ADDRCONF(NETDEV_CHANGE): veth1_macvtap: link becomes ready
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000562dd8f42c30 CR3: 0000000094f6d000 CR4: 00000000001406e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
syzbot
Aug 2, 2020, 5:07:19 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=17d04d0c900000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=15aa480a900000
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+c95f9a...@syzkaller.appspotmail.com
audit: type=1400 audit(1596359102.905:8): avc: denied { execmem } for pid=6370 comm="syz-executor405" scontext=system_u:system_r:kernel_t:s0 tcontext=system_u:system_r:kernel_t:s0 tclass=process permissive=1
IPVS: ftp: loaded support on port[0] = 21
task: ffff88808e932680 task.stack: ffff888097a20000
RAX: dffffc0000000000 RBX: 0000000000000000 RCX: 1ffff11011d265f0
R10: 0000000000000000 R11: ffff88808e932680 R12: ffff8880970455a8
R13: 00000000000000c8 R14: ffff88809624c5cb R15: ffff888097044650
---[ end trace 9f492bad5c0ab83c ]---
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=c95f9a03e069d5406cfa
compiler: gcc (GCC) 10.1.0-syz 20200507
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1496b724900000
dashboard link: https://syzkaller.appspot.com/bug?extid=c95f9a03e069d5406cfa
compiler: gcc (GCC) 10.1.0-syz 20200507
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=15aa480a900000
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+c95f9a...@syzkaller.appspotmail.com
IPVS: ftp: loaded support on port[0] = 21
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
Modules linked in:
CPU: 1 PID: 6400 Comm: kworker/u5:2 Not tainted 4.14.191-syzkaller #0
kasan: GPF could be caused by NULL-ptr deref or user memory access
general protection fault: 0000 [#1] PREEMPT SMP KASAN
Modules linked in:
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
Workqueue: hci0 hci_rx_work
task: ffff88808e932680 task.stack: ffff888097a20000
RIP: 0010:hci_phy_link_complete_evt.isra.0+0x1f3/0x6c0 net/bluetooth/hci_event.c:4360
RSP: 0018:ffff888097a27ad0 EFLAGS: 00010202
RAX: dffffc0000000000 RBX: 0000000000000000 RCX: 1ffff11011d265f0
RDX: 0000000000000002 RSI: 0000000000000004 RDI: 0000000000000010
RBP: ffff88809724ed40 R08: 0000000000000000 R09: 0000000000000003
R10: 0000000000000000 R11: ffff88808e932680 R12: ffff8880970455a8
R13: 00000000000000c8 R14: ffff88809624c5cb R15: ffff888097044650
FS: 0000000000000000(0000) GS:ffff8880aeb00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000000020000000 CR3: 000000009f342000 CR4: 00000000001406e0
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
hci_event_packet+0x2592/0x7c7a net/bluetooth/hci_event.c:5429
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
Code: fa 48 c1 ea 03 80 3c 02 00 0f 85 dd 04 00 00 48 8b 9d 40 08 00 00 48 b8 00 00 00 00 00 fc ff df 48 8d 7b 10 48 89 fa 48 c1 ea 03 <80> 3c 02 00 0f 85 a0 04 00 00 48 b8 00 00 00 00 00 fc ff df 48
RIP: hci_phy_link_complete_evt.isra.0+0x1f3/0x6c0 net/bluetooth/hci_event.c:4360 RSP: ffff888097a27ad0
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
hci_event_packet+0x2592/0x7c7a net/bluetooth/hci_event.c:5429
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
Code: fa 48 c1 ea 03 80 3c 02 00 0f 85 dd 04 00 00 48 8b 9d 40 08 00 00 48 b8 00 00 00 00 00 fc ff df 48 8d 7b 10 48 89 fa 48 c1 ea 03 <80> 3c 02 00 0f 85 a0 04 00 00 48 b8 00 00 00 00 00 fc ff df 48
---[ end trace 9f492bad5c0ab83c ]---
syzbot
Aug 2, 2020, 5:16:16 AM8/2/20
to syzkaller...@googlegroups.com
syzbot has found a reproducer for the following issue on:
HEAD commit: 13af6c74 Linux 4.19.136
git tree: linux-4.19.y
console output: https://syzkaller.appspot.com/x/log.txt?x=11c73292900000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=169030ec900000
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+477d30...@syzkaller.appspotmail.com
audit: type=1400 audit(1596359632.027:8): avc: denied { execmem } for pid=6434 comm="syz-executor651" scontext=system_u:system_r:kernel_t:s0 tcontext=system_u:system_r:kernel_t:s0 tclass=process permissive=1
HEAD commit: 13af6c74 Linux 4.19.136
git tree: linux-4.19.y
kernel config: https://syzkaller.appspot.com/x/.config?x=5b7578d3b5457a49
dashboard link: https://syzkaller.appspot.com/bug?extid=477d30719250034f2009
compiler: gcc (GCC) 10.1.0-syz 20200507
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=17d00398900000
dashboard link: https://syzkaller.appspot.com/bug?extid=477d30719250034f2009
compiler: gcc (GCC) 10.1.0-syz 20200507
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=169030ec900000
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+477d30...@syzkaller.appspotmail.com
IPVS: ftp: loaded support on port[0] = 21
kasan: CONFIG_KASAN_INLINE enabled
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: 1226 Comm: kworker/u5:0 Not tainted 4.19.136-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
Workqueue: hci0 hci_rx_work
RIP: 0010:hci_phy_link_complete_evt.isra.0+0x24a/0x7a0 net/bluetooth/hci_event.c:4682
Code: 48 c1 ea 03 80 3c 02 00 0f 85 60 05 00 00 48 8b 9d 28 08 00 00 48 b8 00 00 00 00 00 fc ff df 48 8d 7b 10 48 89 fa 48 c1 ea 03 <80> 3c 02 00 0f 85 23 05 00 00 48 b8 00 00 00 00 00 fc ff df 48 8b
RSP: 0018:ffff8880a75dfa78 EFLAGS: 00010202
Workqueue: hci0 hci_rx_work
RIP: 0010:hci_phy_link_complete_evt.isra.0+0x24a/0x7a0 net/bluetooth/hci_event.c:4682
Code: 48 c1 ea 03 80 3c 02 00 0f 85 60 05 00 00 48 8b 9d 28 08 00 00 48 b8 00 00 00 00 00 fc ff df 48 8d 7b 10 48 89 fa 48 c1 ea 03 <80> 3c 02 00 0f 85 23 05 00 00 48 b8 00 00 00 00 00 fc ff df 48 8b
RAX: dffffc0000000000 RBX: 0000000000000000 RCX: ffffffff867c041f
RDX: 0000000000000002 RSI: ffffffff867c042c RDI: 0000000000000010
RBP: ffff888089848580 R08: 0000000000000000 R09: 0000000000000000
RDX: 0000000000000002 RSI: ffffffff867c042c RDI: 0000000000000010
R10: 0000000000000001 R11: 0000000000000000 R12: dffffc0000000000
R13: ffff88808537de80 R14: 00000000000000c8 R15: ffff88808537cf50
FS: 0000000000000000(0000) GS:ffff8880ae600000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000055d53655dea0 CR3: 0000000008c6d000 CR4: 00000000001406f0
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
hci_event_packet+0x1973/0x858f net/bluetooth/hci_event.c:5898
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
Modules linked in:
---[ end trace 3aed1ec5c0911ca7 ]---
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
hci_event_packet+0x1973/0x858f net/bluetooth/hci_event.c:5898
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
Modules linked in:
RIP: 0010:hci_phy_link_complete_evt.isra.0+0x24a/0x7a0 net/bluetooth/hci_event.c:4682
Code: 48 c1 ea 03 80 3c 02 00 0f 85 60 05 00 00 48 8b 9d 28 08 00 00 48 b8 00 00 00 00 00 fc ff df 48 8d 7b 10 48 89 fa 48 c1 ea 03 <80> 3c 02 00 0f 85 23 05 00 00 48 b8 00 00 00 00 00 fc ff df 48 8b
RSP: 0018:ffff8880a75dfa78 EFLAGS: 00010202
Code: 48 c1 ea 03 80 3c 02 00 0f 85 60 05 00 00 48 8b 9d 28 08 00 00 48 b8 00 00 00 00 00 fc ff df 48 8d 7b 10 48 89 fa 48 c1 ea 03 <80> 3c 02 00 0f 85 23 05 00 00 48 b8 00 00 00 00 00 fc ff df 48 8b
RAX: dffffc0000000000 RBX: 0000000000000000 RCX: ffffffff867c041f
RDX: 0000000000000002 RSI: ffffffff867c042c RDI: 0000000000000010
RBP: ffff888089848580 R08: 0000000000000000 R09: 0000000000000000
RDX: 0000000000000002 RSI: ffffffff867c042c RDI: 0000000000000010
R10: 0000000000000001 R11: 0000000000000000 R12: dffffc0000000000
R13: ffff88808537de80 R14: 00000000000000c8 R15: ffff88808537cf50
FS: 0000000000000000(0000) GS:ffff8880ae600000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000055d53655dea0 CR3: 0000000008c6d000 CR4: 00000000001406f0
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
syzbot
Jan 21, 2021, 3:41:12 PM1/21/21
to syzkaller...@googlegroups.com
syzbot suspects this issue was fixed by commit:
commit abae100355c011d14c75cabbf9eb773c231187ee
Author: Anmol Karn <anmol.k...@gmail.com>
Date: Wed Sep 30 14:18:13 2020 +0000
Bluetooth: Fix null pointer dereference in hci_event_packet()
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=12812044d00000
start commit: 31acccdc Linux 4.19.157
git tree: linux-4.19.y
kernel config: https://syzkaller.appspot.com/x/.config?x=1f604e014c43fe09
dashboard link: https://syzkaller.appspot.com/bug?extid=477d30719250034f2009
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=15b88b72500000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1683b7be500000
If the result looks correct, please mark the issue as fixed by replying with:
#syz fix: Bluetooth: Fix null pointer dereference in hci_event_packet()
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
commit abae100355c011d14c75cabbf9eb773c231187ee
Author: Anmol Karn <anmol.k...@gmail.com>
Date: Wed Sep 30 14:18:13 2020 +0000
Bluetooth: Fix null pointer dereference in hci_event_packet()
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=12812044d00000
start commit: 31acccdc Linux 4.19.157
git tree: linux-4.19.y
kernel config: https://syzkaller.appspot.com/x/.config?x=1f604e014c43fe09
dashboard link: https://syzkaller.appspot.com/bug?extid=477d30719250034f2009
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=15b88b72500000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1683b7be500000
If the result looks correct, please mark the issue as fixed by replying with:
#syz fix: Bluetooth: Fix null pointer dereference in hci_event_packet()
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
syzbot
Jan 25, 2021, 4:25:08 PM1/25/21
to syzkaller...@googlegroups.com
syzbot suspects this issue was fixed by commit:
commit 4113f6f73f6e8d215609bde8c0c14ca9f8a476c5
Author: Anmol Karn <anmol.k...@gmail.com>
Date: Wed Sep 30 14:18:13 2020 +0000
Bluetooth: Fix null pointer dereference in hci_event_packet()
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=10bffeb4d00000
Date: Wed Sep 30 14:18:13 2020 +0000
Bluetooth: Fix null pointer dereference in hci_event_packet()
start commit: 2b791501 Linux 4.14.203
git tree: linux-4.14.y
kernel config: https://syzkaller.appspot.com/x/.config?x=e52bb6f2a595a463
dashboard link: https://syzkaller.appspot.com/bug?extid=c95f9a03e069d5406cfa
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=116fbc0c500000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=138af40c500000
Reply all
Reply to author
Forward
0 new messages