From: Chen Zhongjin <chenzhongjin@huawei.com>
To: <syzbot+2f9183cb6f89b0e16586@syzkaller.appspotmail.com>,
<syzkaller-bugs@googlegroups.com>, <netdev@vger.kernel.org>,
<stable@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Cc: <jhs@mojatatu.com>, <xiyou.wangcong@gmail.com>,
<jiri@resnulli.us>, <davem@davemloft.net>, <edumazet@google.com>,
<kuba@kernel.org>, <pabeni@redhat.com>,
<gregkh@linuxfoundation.org>
Subject: Re: [PATCH net] net/sched: Fix memory leak in tcindex_set_parms
Date: Thu, 8 Dec 2022 14:35:37 +0800 [thread overview]
Message-ID: <ad702330-d0da-c096-0f37-1cb4e866ddae@huawei.com> (raw)
In-Reply-To: <20221208032216.63513-1-chenzhongjin@huawei.com>
Hi,
On 2022/12/8 11:22, Chen Zhongjin wrote:
> syzkaller reported a memleak:
> https://syzkaller.appspot.com/bug?id=e061e6cd46417ee6566dc249d8f982c0b5977a52
>
> unreferenced object 0xffff888107813900 (size 256):
> backtrace:
> kcalloc include/linux/slab.h:636 [inline]
> tcf_exts_init include/net/pkt_cls.h:250 [inline]
> tcindex_set_parms+0xa7/0xbe0 net/sched/cls_tcindex.c:342
> tcindex_change+0xdf/0x120 net/sched/cls_tcindex.c:553
> tc_new_tfilter+0x4f2/0x1100 net/sched/cls_api.c:2147
> ...
>
> The reproduce calls tc_new_tfilter() continuously:
>
> tc_new_tfilter()...
> tcindex_set_parms()
> tcf_exts_init(&e, ...) // alloc e->actions
> tcf_exts_change(&r->exts, &e)
>
> tc_new_tfilter()...
> tcindex_set_parms()
> old_r = r // same as first r
> tcindex_filter_result_init(old_r, cp, net);
> // old_r is holding e->actions but here it calls memset(old_r, 0)
> // so the previous e->actions is leaked
>
> So here tcf_exts_destroy() should be called to free old_r->exts.actions
> before memset(old_r, 0) sets it to NULL.
>
> Fixes: 1da177e4c3f4 ("Linux-2.6.12-rc2")
> Cc: stable@vger.kernel.org
> Reported-by: syzbot+2f9183cb6f89b0e16586@syzkaller.appspotmail.com
> Signed-off-by: Chen Zhongjin <chenzhongjin@huawei.com>
> ---
> #syz test https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git 355479c70a48
> ---
> net/sched/cls_tcindex.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/net/sched/cls_tcindex.c b/net/sched/cls_tcindex.c
> index 1c9eeb98d826..00a6c04a4b42 100644
> --- a/net/sched/cls_tcindex.c
> +++ b/net/sched/cls_tcindex.c
> @@ -479,6 +479,7 @@ tcindex_set_parms(struct net *net, struct tcf_proto *tp, unsigned long base,
> }
>
> if (old_r && old_r != r) {
> + tcf_exts_destroy(&old_r->exts);
> err = tcindex_filter_result_init(old_r, cp, net);
> if (err < 0) {
> kfree(f);
Just noticed that Hawkins has sent a patch for this. Please ignore mine.
Thanks!
next prev parent reply other threads:[~2022-12-08 6:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-08 3:22 Chen Zhongjin
2022-12-08 6:35 ` Chen Zhongjin [this message]
2022-12-08 11:06 ` [syzbot] memory leak in tcindex_set_parms (3) syzbot
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=ad702330-d0da-c096-0f37-1cb4e866ddae@huawei.com \
--to=chenzhongjin@huawei.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=gregkh@linuxfoundation.org \
--cc=jhs@mojatatu.com \
--cc=jiri@resnulli.us \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=stable@vger.kernel.org \
--cc=syzbot+2f9183cb6f89b0e16586@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=xiyou.wangcong@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
all inboxes | Powered by JetHome®