From: syzbot <syzbot+276ca1c77a19977c0130@syzkaller.appspotmail.com>
To: davem@davemloft.net, linux-kernel@vger.kernel.org,
linux-sctp@vger.kernel.org, marcelo.leitner@gmail.com,
netdev@vger.kernel.org, nhorman@tuxdriver.com,
syzkaller-bugs@googlegroups.com, vyasevich@gmail.com
Subject: memory leak in sctp_v6_create_accept_sk
Date: Sun, 02 Jun 2019 13:22:05 -0700 [thread overview]
Message-ID: <0000000000004c134d058a5d0096@google.com> (raw)
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@syzkaller.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@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
reply other threads:[~2019-06-02 20:22 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=0000000000004c134d058a5d0096@google.com \
--to=syzbot+276ca1c77a19977c0130@syzkaller.appspotmail.com \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sctp@vger.kernel.org \
--cc=marcelo.leitner@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=nhorman@tuxdriver.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=vyasevich@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).