lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Date:   Thu, 01 Mar 2018 00:44:02 -0800
From:   syzbot <syzbot+9605e6cace1b5efd4a0a@...kaller.appspotmail.com>
To:     davem@...emloft.net, linux-kernel@...r.kernel.org,
        linux-s390@...r.kernel.org, netdev@...r.kernel.org,
        syzkaller-bugs@...glegroups.com, ubraun@...ux.vnet.ibm.com
Subject: general protection fault in smc_getname

Hello,

syzbot hit the following crash on net-next commit
f74290fdb363665538743d14c4f00aeacdb68d87 (Sat Feb 24 05:04:20 2018 +0000)
Merge git://git.kernel.org/pub/scm/linux/kernel/git/davem/net

So far this crash happened 3 times on net-next.
Unfortunately, I don't have any reproducer for this crash yet.
Raw console output is attached.
compiler: gcc (GCC) 7.1.1 20170620
.config is attached.

IMPORTANT: if you fix the bug, please add the following tag to the commit:
Reported-by: syzbot+9605e6cace1b5efd4a0a@...kaller.appspotmail.com
It will help syzbot understand when the bug is fixed. See footer for  
details.
If you forward the report, please keep this part and the footer.

kasan: CONFIG_KASAN_INLINE enabled
kasan: GPF could be caused by NULL-ptr deref or user memory access
general protection fault: 0000 [#1] SMP KASAN
Dumping ftrace buffer:
    (ftrace buffer empty)
Modules linked in:
CPU: 0 PID: 27049 Comm: syz-executor5 Not tainted 4.16.0-rc2+ #241
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS  
Google 01/01/2011
RIP: 0010:smc_getname+0x88/0x190 net/smc/af_smc.c:1087
RSP: 0018:ffff8801ca9afc08 EFLAGS: 00010206
RAX: dffffc0000000000 RBX: 0000000000000000 RCX: ffffffff85a46dfa
kasan: CONFIG_KASAN_INLINE enabled
RDX: 0000000000000005 RSI: ffffc90002d29000 RDI: 0000000000000028
RBP: ffff8801ca9afc28 R08: 0000000000000000 R09: 1ffff10039535f09
R10: 0000000000000003 R11: 0000000000000000 R12: 0000000000000000
R13: ffff8801ca9afcf0 R14: ffff8801c72a7b00 R15: ffff8801ca9afcf0
FS:  00007f935687c700(0000) GS:ffff8801db200000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
kasan: GPF could be caused by NULL-ptr deref or user memory access
CR2: 0000000000464a60 CR3: 00000001b2115001 CR4: 00000000001606f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
  SYSC_getsockname+0x15d/0x360 net/socket.c:1668
  SyS_getsockname+0x24/0x30 net/socket.c:1653
  do_syscall_64+0x280/0x940 arch/x86/entry/common.c:287
  entry_SYSCALL_64_after_hwframe+0x42/0xb7
RIP: 0033:0x453de9
RSP: 002b:00007f935687bc68 EFLAGS: 00000246 ORIG_RAX: 0000000000000033
RAX: ffffffffffffffda RBX: 00007f935687c6d4 RCX: 0000000000453de9
RDX: 0000000020000080 RSI: 0000000020000000 RDI: 0000000000000013
RBP: 000000000072bf58 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 00000000ffffffff
R13: 00000000000000c2 R14: 00000000006f12d0 R15: 0000000000000001
Code: fa 48 c1 ea 03 80 3c 02 00 0f 85 e6 00 00 00 48 8b 9b 50 04 00 00 48  
b8 00 00 00 00 00 fc ff df 48 8d 7b 28 48 89 fa 48 c1 ea 03 <80> 3c 02 00  
0f 85 e8 00 00 00 4c 8b 73 28 48 b8 00 00 00 00 00
RIP: smc_getname+0x88/0x190 net/smc/af_smc.c:1087 RSP: ffff8801ca9afc08
general protection fault: 0000 [#2] SMP KASAN
---[ end trace 350f89cd50a2ad8e ]---
Dumping ftrace buffer:
    (ftrace buffer empty)
Modules linked in:
Kernel panic - not syncing: Fatal exception
CPU: 1 PID: 27056 Comm: syz-executor5 Tainted: G      D           
4.16.0-rc2+ #241
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS  
Google 01/01/2011
RIP: 0010:smc_getname+0x88/0x190 net/smc/af_smc.c:1087
RSP: 0018:ffff8801bf097c08 EFLAGS: 00010206
RAX: dffffc0000000000 RBX: 0000000000000000 RCX: ffffffff85a46dfa
RDX: 0000000000000005 RSI: ffffc90003ecc000 RDI: 0000000000000028
RBP: ffff8801bf097c28 R08: 0000000000000000 R09: 1ffff10037e12f09
R10: 0000000000000003 R11: ffffed0037e12f43 R12: 0000000000000000
R13: ffff8801bf097cf0 R14: ffff8801cda38180 R15: ffff8801bf097cf0
FS:  00007f9356819700(0000) GS:ffff8801db300000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f9356818db8 CR3: 00000001b2115003 CR4: 00000000001606e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
  SYSC_getsockname+0x15d/0x360 net/socket.c:1668
  SyS_getsockname+0x24/0x30 net/socket.c:1653
  do_syscall_64+0x280/0x940 arch/x86/entry/common.c:287
  entry_SYSCALL_64_after_hwframe+0x42/0xb7
RIP: 0033:0x453de9
RSP: 002b:00007f9356818c68 EFLAGS: 00000246 ORIG_RAX: 0000000000000033
RAX: ffffffffffffffda RBX: 00007f93568196d4 RCX: 0000000000453de9
RDX: 0000000020000080 RSI: 0000000020000000 RDI: 0000000000000015
RBP: 000000000072c180 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 00000000ffffffff
R13: 00000000000000c2 R14: 00000000006f12d0 R15: 0000000000000004
Code: fa 48 c1 ea 03 80 3c 02 00 0f 85 e6 00 00 00 48 8b 9b 50 04 00 00 48  
b8 00 00 00 00 00 fc ff df 48 8d 7b 28 48 89 fa 48 c1 ea 03 <80> 3c 02 00  
0f 85 e8 00 00 00 4c 8b 73 28 48 b8 00 00 00 00 00
RIP: smc_getname+0x88/0x190 net/smc/af_smc.c:1087 RSP: ffff8801bf097c08
Dumping ftrace buffer:
    (ftrace buffer empty)
Kernel Offset: disabled
Rebooting in 86400 seconds..


---
This bug is generated by a dumb bot. It may contain errors.
See https://goo.gl/tpsmEJ for details.
Direct all questions to syzkaller@...glegroups.com.

syzbot will keep track of this bug report.
If you forgot to add the Reported-by tag, once the fix for this bug is  
merged
into any tree, please reply to this email with:
#syz fix: exact-commit-title
To mark this as a duplicate of another syzbot report, please reply with:
#syz dup: exact-subject-of-another-report
If it's a one-off invalid bug report, please reply with:
#syz invalid
Note: if the crash happens again, it will cause creation of a new bug  
report.
Note: all commands must start from beginning of the line in the email body.

View attachment "raw.log.txt" of type "text/plain" (1048576 bytes)

View attachment "config.txt" of type "text/plain" (137464 bytes)

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ