From: syzbot <syzbot+96e916d6f6f7617bc9fc@syzkaller.appspotmail.com>
To: davem@davemloft.net, kuba@kernel.org,
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_stream_init_ext (2)
Date: Fri, 17 Apr 2020 03:45:10 +0000 [thread overview]
Message-ID: <0000000000004373bc05a37460df@google.com> (raw)
Hello,
syzbot found the following crash on:
HEAD commit: 00086336 Merge tag 'efi-urgent-2020-04-15' of git://git.ke..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x\x12996107e00000
kernel config: https://syzkaller.appspot.com/x/.config?xïff978b972fb2c
dashboard link: https://syzkaller.appspot.com/bug?extid–e916d6f6f7617bc9fc
compiler: gcc (GCC) 9.0.0 20181231 (experimental)
syz repro: https://syzkaller.appspot.com/x/repro.syz?x\x137ddf3fe00000
IMPORTANT: if you fix the bug, please add the following tag to the commit:
Reported-by: syzbot+96e916d6f6f7617bc9fc@syzkaller.appspotmail.com
BUG: memory leak
unreferenced object 0xffff888103ba4580 (size 96):
comm "syz-executor.1", pid 8335, jiffies 4294953411 (age 14.410s)
hex dump (first 32 bytes):
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
backtrace:
[<00000000b06f3e80>] kmalloc include/linux/slab.h:555 [inline]
[<00000000b06f3e80>] kzalloc include/linux/slab.h:669 [inline]
[<00000000b06f3e80>] sctp_stream_init_ext+0x28/0xe0 net/sctp/stream.c:162
[<00000000aff2ecba>] sctp_sendmsg_to_asoc+0x9af/0xab0 net/sctp/socket.c:1811
[<00000000d5d5eb76>] sctp_sendmsg+0x2a6/0xc60 net/sctp/socket.c:2031
[<0000000023cdbfa3>] inet_sendmsg+0x39/0x60 net/ipv4/af_inet.c:807
[<00000000885878ef>] sock_sendmsg_nosec net/socket.c:652 [inline]
[<00000000885878ef>] sock_sendmsg+0x4c/0x60 net/socket.c:672
[<0000000009d727e5>] __sys_sendto+0x11d/0x1c0 net/socket.c:2000
[<0000000066974477>] __do_sys_sendto net/socket.c:2012 [inline]
[<0000000066974477>] __se_sys_sendto net/socket.c:2008 [inline]
[<0000000066974477>] __x64_sys_sendto+0x26/0x30 net/socket.c:2008
[<00000000ecc1fea9>] do_syscall_64+0x6e/0x220 arch/x86/entry/common.c:295
[<00000000605d798b>] 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
WARNING: multiple messages have this Message-ID (diff)
From: syzbot <syzbot+96e916d6f6f7617bc9fc@syzkaller.appspotmail.com>
To: davem@davemloft.net, kuba@kernel.org,
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_stream_init_ext (2)
Date: Thu, 16 Apr 2020 20:45:10 -0700 [thread overview]
Message-ID: <0000000000004373bc05a37460df@google.com> (raw)
Hello,
syzbot found the following crash on:
HEAD commit: 00086336 Merge tag 'efi-urgent-2020-04-15' of git://git.ke..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=12996107e00000
kernel config: https://syzkaller.appspot.com/x/.config?x=efff978b972fb2c
dashboard link: https://syzkaller.appspot.com/bug?extid=96e916d6f6f7617bc9fc
compiler: gcc (GCC) 9.0.0 20181231 (experimental)
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=137ddf3fe00000
IMPORTANT: if you fix the bug, please add the following tag to the commit:
Reported-by: syzbot+96e916d6f6f7617bc9fc@syzkaller.appspotmail.com
BUG: memory leak
unreferenced object 0xffff888103ba4580 (size 96):
comm "syz-executor.1", pid 8335, jiffies 4294953411 (age 14.410s)
hex dump (first 32 bytes):
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
backtrace:
[<00000000b06f3e80>] kmalloc include/linux/slab.h:555 [inline]
[<00000000b06f3e80>] kzalloc include/linux/slab.h:669 [inline]
[<00000000b06f3e80>] sctp_stream_init_ext+0x28/0xe0 net/sctp/stream.c:162
[<00000000aff2ecba>] sctp_sendmsg_to_asoc+0x9af/0xab0 net/sctp/socket.c:1811
[<00000000d5d5eb76>] sctp_sendmsg+0x2a6/0xc60 net/sctp/socket.c:2031
[<0000000023cdbfa3>] inet_sendmsg+0x39/0x60 net/ipv4/af_inet.c:807
[<00000000885878ef>] sock_sendmsg_nosec net/socket.c:652 [inline]
[<00000000885878ef>] sock_sendmsg+0x4c/0x60 net/socket.c:672
[<0000000009d727e5>] __sys_sendto+0x11d/0x1c0 net/socket.c:2000
[<0000000066974477>] __do_sys_sendto net/socket.c:2012 [inline]
[<0000000066974477>] __se_sys_sendto net/socket.c:2008 [inline]
[<0000000066974477>] __x64_sys_sendto+0x26/0x30 net/socket.c:2008
[<00000000ecc1fea9>] do_syscall_64+0x6e/0x220 arch/x86/entry/common.c:295
[<00000000605d798b>] 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
next reply other threads:[~2020-04-17 3:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-17 3:45 syzbot [this message]
2020-04-17 3:45 ` memory leak in sctp_stream_init_ext (2) syzbot
[not found] ` <20200417083224.13400-1-hdanton@sina.com>
2020-04-17 13:31 ` Marcelo Ricardo Leitner
2020-04-17 13:31 ` Marcelo Ricardo Leitner
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=0000000000004373bc05a37460df@google.com \
--to=syzbot+96e916d6f6f7617bc9fc@syzkaller.appspotmail.com \
--cc=davem@davemloft.net \
--cc=kuba@kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.