netdev - memory leak in sctp_v6_create_accept

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>] [day] [month] [year] [list]

Date:   Sun, 02 Jun 2019 13:22:05 -0700
From:   syzbot <syzbot+276ca1c77a19977c0130@...kaller.appspotmail.com>
To:     davem@...emloft.net, linux-kernel@...r.kernel.org,
        linux-sctp@...r.kernel.org, marcelo.leitner@...il.com,
        netdev@...r.kernel.org, nhorman@...driver.com,
        syzkaller-bugs@...glegroups.com, vyasevich@...il.com
Subject: memory leak in sctp_v6_create_accept_sk

Hello,

syzbot found the following crash on:

HEAD commit:    3ab4436f Merge tag 'nfsd-5.2-1' of git://linux-nfs.org/~bf..
git tree:       upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=153c64a6a00000
kernel config:  https://syzkaller.appspot.com/x/.config?x=50393f7bfe444ff6
dashboard link: https://syzkaller.appspot.com/bug?extid=276ca1c77a19977c0130
compiler:       gcc (GCC) 9.0.0 20181231 (experimental)
syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=16195636a00000
C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=1717d286a00000

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

ffffffffda RBX: 00000000006fbc38 RCX: 0000000000446b59
BUG: memory leak
unreferenced object 0xffff88812382ec40 (size 1512):
   comm "syz-executor098", pid 7138, jiffies 4294945165 (age 7.780s)
   hex dump (first 32 bytes):
     00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
     0a 00 07 40 00 00 00 00 00 00 00 00 00 00 00 00  ...@............
   backtrace:
     [<0000000006e93bd5>] kmemleak_alloc_recursive  
include/linux/kmemleak.h:55 [inline]
     [<0000000006e93bd5>] slab_post_alloc_hook mm/slab.h:439 [inline]
     [<0000000006e93bd5>] slab_alloc mm/slab.c:3326 [inline]
     [<0000000006e93bd5>] kmem_cache_alloc+0x134/0x270 mm/slab.c:3488
     [<000000007da542cd>] sk_prot_alloc+0x41/0x170 net/core/sock.c:1596
     [<00000000a4eabe8a>] sk_alloc+0x35/0x2f0 net/core/sock.c:1656
     [<0000000053fa015e>] sctp_v6_create_accept_sk+0x5c/0x1b0  
net/sctp/ipv6.c:711
     [<000000008c31091c>] sctp_accept+0x1df/0x290 net/sctp/socket.c:4913
     [<00000000ec8d71b8>] inet_accept+0x4e/0x1d0 net/ipv4/af_inet.c:734
     [<000000001f5fe485>] __sys_accept4+0x12a/0x280 net/socket.c:1760
     [<0000000070a98ea5>] __do_sys_accept net/socket.c:1801 [inline]
     [<0000000070a98ea5>] __se_sys_accept net/socket.c:1798 [inline]
     [<0000000070a98ea5>] __x64_sys_accept+0x20/0x30 net/socket.c:1798
     [<000000004a076fbd>] do_syscall_64+0x76/0x1a0  
arch/x86/entry/common.c:301
     [<00000000d752b65c>] entry_SYSCALL_64_after_hwframe+0x44/0xa9



---
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 syzkaller@...glegroups.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