From: syzbot <syzbot+a24c5252f3e3ab733464@syzkaller.appspotmail.com>
To: bridge@lists.linux-foundation.org, coreteam@netfilter.org,
davem@davemloft.net, edumazet@google.com, fw@strlen.de,
kadlec@netfilter.org, kuba@kernel.org,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
netfilter-devel@vger.kernel.org, pabeni@redhat.com,
pablo@netfilter.org, razor@blackwall.org, roopa@nvidia.com,
syzkaller-bugs@googlegroups.com
Subject: [Bridge] [syzbot] memory leak in do_replace
Date: Mon, 19 Sep 2022 16:27:38 -0700 [thread overview]
Message-ID: <000000000000b010bd05e9100e11@google.com> (raw)
Hello,
syzbot found the following issue on:
HEAD commit: 3245cb65fd91 Merge tag 'devicetree-fixes-for-6.0-2' of git..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=17a88ef7080000
kernel config: https://syzkaller.appspot.com/x/.config?x=a4afe4efcad47dde
dashboard link: https://syzkaller.appspot.com/bug?extid=a24c5252f3e3ab733464
compiler: gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=14b0e87f080000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1100f1d8880000
Downloadable assets:
disk image: https://storage.googleapis.com/2d6c9d59c55a/disk-3245cb65.raw.xz
vmlinux: https://storage.googleapis.com/0f52632026ad/vmlinux-3245cb65.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+a24c5252f3e3ab733464@syzkaller.appspotmail.com
executing program
executing program
executing program
executing program
BUG: memory leak
unreferenced object 0xffffc90000ded000 (size 4096):
comm "syz-executor317", pid 3615, jiffies 4294946120 (age 22.550s)
hex dump (first 32 bytes):
90 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:
[<ffffffff8153105f>] __vmalloc_node_range+0xb3f/0xbd0 mm/vmalloc.c:3224
[<ffffffff81531239>] __vmalloc_node mm/vmalloc.c:3261 [inline]
[<ffffffff81531239>] __vmalloc+0x49/0x50 mm/vmalloc.c:3275
[<ffffffff83e28027>] do_replace+0x197/0x340 net/bridge/netfilter/ebtables.c:1131
[<ffffffff83e2880c>] do_ebt_set_ctl+0x22c/0x310 net/bridge/netfilter/ebtables.c:2520
[<ffffffff83a3fb68>] nf_setsockopt+0x68/0xa0 net/netfilter/nf_sockopt.c:101
[<ffffffff83bb5d69>] ip_setsockopt+0x259/0x2040 net/ipv4/ip_sockglue.c:1444
[<ffffffff83bcbe10>] tcp_setsockopt+0x70/0x1430 net/ipv4/tcp.c:3789
[<ffffffff8425d1d8>] smc_setsockopt+0xd8/0x5c0 net/smc/af_smc.c:2941
[<ffffffff8386dd2b>] __sys_setsockopt+0x1ab/0x380 net/socket.c:2252
[<ffffffff8386df22>] __do_sys_setsockopt net/socket.c:2263 [inline]
[<ffffffff8386df22>] __se_sys_setsockopt net/socket.c:2260 [inline]
[<ffffffff8386df22>] __x64_sys_setsockopt+0x22/0x30 net/socket.c:2260
[<ffffffff845eab35>] do_syscall_x64 arch/x86/entry/common.c:50 [inline]
[<ffffffff845eab35>] do_syscall_64+0x35/0xb0 arch/x86/entry/common.c:80
[<ffffffff84800087>] entry_SYSCALL_64_after_hwframe+0x63/0xcd
BUG: memory leak
unreferenced object 0xffffc90000df5000 (size 4096):
comm "syz-executor317", pid 3615, jiffies 4294946120 (age 22.550s)
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:
[<ffffffff8153105f>] __vmalloc_node_range+0xb3f/0xbd0 mm/vmalloc.c:3224
[<ffffffff81531239>] __vmalloc_node mm/vmalloc.c:3261 [inline]
[<ffffffff81531239>] __vmalloc+0x49/0x50 mm/vmalloc.c:3275
[<ffffffff83e28071>] do_replace+0x1e1/0x340 net/bridge/netfilter/ebtables.c:1138
[<ffffffff83e2880c>] do_ebt_set_ctl+0x22c/0x310 net/bridge/netfilter/ebtables.c:2520
[<ffffffff83a3fb68>] nf_setsockopt+0x68/0xa0 net/netfilter/nf_sockopt.c:101
[<ffffffff83bb5d69>] ip_setsockopt+0x259/0x2040 net/ipv4/ip_sockglue.c:1444
[<ffffffff83bcbe10>] tcp_setsockopt+0x70/0x1430 net/ipv4/tcp.c:3789
[<ffffffff8425d1d8>] smc_setsockopt+0xd8/0x5c0 net/smc/af_smc.c:2941
[<ffffffff8386dd2b>] __sys_setsockopt+0x1ab/0x380 net/socket.c:2252
[<ffffffff8386df22>] __do_sys_setsockopt net/socket.c:2263 [inline]
[<ffffffff8386df22>] __se_sys_setsockopt net/socket.c:2260 [inline]
[<ffffffff8386df22>] __x64_sys_setsockopt+0x22/0x30 net/socket.c:2260
[<ffffffff845eab35>] do_syscall_x64 arch/x86/entry/common.c:50 [inline]
[<ffffffff845eab35>] do_syscall_64+0x35/0xb0 arch/x86/entry/common.c:80
[<ffffffff84800087>] entry_SYSCALL_64_after_hwframe+0x63/0xcd
---
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 syzkaller@googlegroups.com.
syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.
syzbot can test patches for this issue, for details see:
https://goo.gl/tpsmEJ#testing-patches
WARNING: multiple messages have this Message-ID (diff)
From: syzbot <syzbot+a24c5252f3e3ab733464@syzkaller.appspotmail.com>
To: bridge@lists.linux-foundation.org, coreteam@netfilter.org,
davem@davemloft.net, edumazet@google.com, fw@strlen.de,
kadlec@netfilter.org, kuba@kernel.org,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
netfilter-devel@vger.kernel.org, pabeni@redhat.com,
pablo@netfilter.org, razor@blackwall.org, roopa@nvidia.com,
syzkaller-bugs@googlegroups.com
Subject: [syzbot] memory leak in do_replace
Date: Mon, 19 Sep 2022 16:27:38 -0700 [thread overview]
Message-ID: <000000000000b010bd05e9100e11@google.com> (raw)
Hello,
syzbot found the following issue on:
HEAD commit: 3245cb65fd91 Merge tag 'devicetree-fixes-for-6.0-2' of git..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=17a88ef7080000
kernel config: https://syzkaller.appspot.com/x/.config?x=a4afe4efcad47dde
dashboard link: https://syzkaller.appspot.com/bug?extid=a24c5252f3e3ab733464
compiler: gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=14b0e87f080000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1100f1d8880000
Downloadable assets:
disk image: https://storage.googleapis.com/2d6c9d59c55a/disk-3245cb65.raw.xz
vmlinux: https://storage.googleapis.com/0f52632026ad/vmlinux-3245cb65.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+a24c5252f3e3ab733464@syzkaller.appspotmail.com
executing program
executing program
executing program
executing program
BUG: memory leak
unreferenced object 0xffffc90000ded000 (size 4096):
comm "syz-executor317", pid 3615, jiffies 4294946120 (age 22.550s)
hex dump (first 32 bytes):
90 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:
[<ffffffff8153105f>] __vmalloc_node_range+0xb3f/0xbd0 mm/vmalloc.c:3224
[<ffffffff81531239>] __vmalloc_node mm/vmalloc.c:3261 [inline]
[<ffffffff81531239>] __vmalloc+0x49/0x50 mm/vmalloc.c:3275
[<ffffffff83e28027>] do_replace+0x197/0x340 net/bridge/netfilter/ebtables.c:1131
[<ffffffff83e2880c>] do_ebt_set_ctl+0x22c/0x310 net/bridge/netfilter/ebtables.c:2520
[<ffffffff83a3fb68>] nf_setsockopt+0x68/0xa0 net/netfilter/nf_sockopt.c:101
[<ffffffff83bb5d69>] ip_setsockopt+0x259/0x2040 net/ipv4/ip_sockglue.c:1444
[<ffffffff83bcbe10>] tcp_setsockopt+0x70/0x1430 net/ipv4/tcp.c:3789
[<ffffffff8425d1d8>] smc_setsockopt+0xd8/0x5c0 net/smc/af_smc.c:2941
[<ffffffff8386dd2b>] __sys_setsockopt+0x1ab/0x380 net/socket.c:2252
[<ffffffff8386df22>] __do_sys_setsockopt net/socket.c:2263 [inline]
[<ffffffff8386df22>] __se_sys_setsockopt net/socket.c:2260 [inline]
[<ffffffff8386df22>] __x64_sys_setsockopt+0x22/0x30 net/socket.c:2260
[<ffffffff845eab35>] do_syscall_x64 arch/x86/entry/common.c:50 [inline]
[<ffffffff845eab35>] do_syscall_64+0x35/0xb0 arch/x86/entry/common.c:80
[<ffffffff84800087>] entry_SYSCALL_64_after_hwframe+0x63/0xcd
BUG: memory leak
unreferenced object 0xffffc90000df5000 (size 4096):
comm "syz-executor317", pid 3615, jiffies 4294946120 (age 22.550s)
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:
[<ffffffff8153105f>] __vmalloc_node_range+0xb3f/0xbd0 mm/vmalloc.c:3224
[<ffffffff81531239>] __vmalloc_node mm/vmalloc.c:3261 [inline]
[<ffffffff81531239>] __vmalloc+0x49/0x50 mm/vmalloc.c:3275
[<ffffffff83e28071>] do_replace+0x1e1/0x340 net/bridge/netfilter/ebtables.c:1138
[<ffffffff83e2880c>] do_ebt_set_ctl+0x22c/0x310 net/bridge/netfilter/ebtables.c:2520
[<ffffffff83a3fb68>] nf_setsockopt+0x68/0xa0 net/netfilter/nf_sockopt.c:101
[<ffffffff83bb5d69>] ip_setsockopt+0x259/0x2040 net/ipv4/ip_sockglue.c:1444
[<ffffffff83bcbe10>] tcp_setsockopt+0x70/0x1430 net/ipv4/tcp.c:3789
[<ffffffff8425d1d8>] smc_setsockopt+0xd8/0x5c0 net/smc/af_smc.c:2941
[<ffffffff8386dd2b>] __sys_setsockopt+0x1ab/0x380 net/socket.c:2252
[<ffffffff8386df22>] __do_sys_setsockopt net/socket.c:2263 [inline]
[<ffffffff8386df22>] __se_sys_setsockopt net/socket.c:2260 [inline]
[<ffffffff8386df22>] __x64_sys_setsockopt+0x22/0x30 net/socket.c:2260
[<ffffffff845eab35>] do_syscall_x64 arch/x86/entry/common.c:50 [inline]
[<ffffffff845eab35>] do_syscall_64+0x35/0xb0 arch/x86/entry/common.c:80
[<ffffffff84800087>] entry_SYSCALL_64_after_hwframe+0x63/0xcd
---
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 syzkaller@googlegroups.com.
syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.
syzbot can test patches for this issue, for details see:
https://goo.gl/tpsmEJ#testing-patches
next reply other threads:[~2022-09-19 23:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-19 23:27 syzbot [this message]
2022-09-19 23:27 ` [syzbot] memory leak in do_replace syzbot
2022-09-20 12:20 ` [PATCH nf] netfilter: ebtables: fix memory leak when blob is malformed Florian Westphal
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=000000000000b010bd05e9100e11@google.com \
--to=syzbot+a24c5252f3e3ab733464@syzkaller.appspotmail.com \
--cc=bridge@lists.linux-foundation.org \
--cc=coreteam@netfilter.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=fw@strlen.de \
--cc=kadlec@netfilter.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=pablo@netfilter.org \
--cc=razor@blackwall.org \
--cc=roopa@nvidia.com \
--cc=syzkaller-bugs@googlegroups.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.