linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: lyl2019@mail.ustc.edu.cn
To: "Leon Romanovsky" <leon@kernel.org>
Cc: dledford@redhat.com, jgg@ziepe.ca, linux-rdma@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: Re: Re: [PATCH] infiniband/core: Fix a use after free in cm_work_handler
Date: Thu, 11 Mar 2021 20:03:23 +0800 (GMT+08:00)	[thread overview]
Message-ID: <f748b4c.c8d4.178212b8650.Coremail.lyl2019@mail.ustc.edu.cn> (raw)
In-Reply-To: <YEn5XxgB1LqQ0PSE@unreal>




> -----原始邮件-----
> 发件人: "Leon Romanovsky" <leon@kernel.org>
> 发送时间: 2021-03-11 19:05:03 (星期四)
> 收件人: lyl2019@mail.ustc.edu.cn
> 抄送: dledford@redhat.com, jgg@ziepe.ca, linux-rdma@vger.kernel.org, linux-kernel@vger.kernel.org
> 主题: Re: Re: [PATCH] infiniband/core: Fix a use after free in cm_work_handler
> 
> On Thu, Mar 11, 2021 at 06:29:19PM +0800, lyl2019@mail.ustc.edu.cn wrote:
> > In the implementation of destory_cm_id(), it restores cm_id_priv by
> > "cm_id_priv = container_of(cm_id, struct iwcm_id_private, id);".
> >
> > And the last line of destory_cm_id() calls "(void)iwcm_deref_id(cm_id_priv);"
> > to free the cm_id_priv.
> 
> It is not enough to see double call to iwcm_deref_id() because it is
> protected with refcount to claim use-after-free. Did you hit the BUG_ON()
> for the second call to iwcm_deref_id()?
> 
> And please don't do top-posting.
> 
> Thanks
> 
> >
> >
> > > -----原始邮件-----
> > > 发件人: "Leon Romanovsky" <leon@kernel.org>
> > > 发送时间: 2021-03-11 17:22:03 (星期四)
> > > 收件人: "Lv Yunlong" <lyl2019@mail.ustc.edu.cn>
> > > 抄送: dledford@redhat.com, jgg@ziepe.ca, linux-rdma@vger.kernel.org, linux-kernel@vger.kernel.org
> > > 主题: Re: [PATCH] infiniband/core: Fix a use after free in cm_work_handler
> > >
> > > On Wed, Mar 10, 2021 at 06:21:53PM -0800, Lv Yunlong wrote:
> > > > In cm_work_handler, it calls destory_cm_id() to release
> > > > the initial reference of cm_id_priv taken by iw_create_cm_id()
> > > > and free the cm_id_priv. After destory_cm_id(), iwcm_deref_id
> > > > (cm_id_priv) will be called and cause a use after free.
> > > >
> > > > Fixes: 59c68ac31e15a ("iw_cm: free cm_id resources on the last deref")
> > > > Signed-off-by: Lv Yunlong <lyl2019@mail.ustc.edu.cn>
> > > > ---
> > > > drivers/infiniband/core/iwcm.c | 4 +++-
> > > > 1 file changed, 3 insertions(+), 1 deletion(-)
> > > >
> > > > diff --git a/drivers/infiniband/core/iwcm.c b/drivers/infiniband/core/iwcm.c
> > > > index da8adadf4755..cb6b4ac45e21 100644
> > > > --- a/drivers/infiniband/core/iwcm.c
> > > > +++ b/drivers/infiniband/core/iwcm.c
> > > > @@ -1035,8 +1035,10 @@ static void cm_work_handler(struct work_struct *_work)
> > > >
> > > > 		if (!test_bit(IWCM_F_DROP_EVENTS, &cm_id_priv->flags)) {
> > > > 			ret = process_event(cm_id_priv, &levent);
> > > > -			if (ret)
> > > > +			if (ret) {
> > > > 				destroy_cm_id(&cm_id_priv->id);
> > > > +				return;
> > >
> > > The destroy_cm_id() is called to free ->id and not cm_id_priv. This "return"
> > > leaks cm_id_priv now and what "a use after free" do you see?
> > >
> > > > +			}
> > > > 		} else
> > > > 			pr_debug("dropping event %d\n", levent.event);
> > > > 		if (iwcm_deref_id(cm_id_priv))
> > > > --
> > > > 2.25.1
> > > >
> > > >

I'm not familiar with debug the kernel, sorry.This problem was
 reported by my code analyzer and reviewed by myself.

But i think as long as destroy_cm_id() is called, iwcm_deref_id() will be called twice.
Then "BUG_ON(atomic_read(&cm_id_priv->refcount)==0);" in iwcm_deref_id() will be triggered.

Is it not a true problem?





  reply	other threads:[~2021-03-11 12:04 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-11  2:21 [PATCH] infiniband/core: Fix a use after free in cm_work_handler Lv Yunlong
2021-03-11  9:22 ` Leon Romanovsky
2021-03-11 10:29   ` lyl2019
2021-03-11 11:05     ` Leon Romanovsky
2021-03-11 12:03       ` lyl2019 [this message]
2021-03-11 14:12         ` Leon Romanovsky

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=f748b4c.c8d4.178212b8650.Coremail.lyl2019@mail.ustc.edu.cn \
    --to=lyl2019@mail.ustc.edu.cn \
    --cc=dledford@redhat.com \
    --cc=jgg@ziepe.ca \
    --cc=leon@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rdma@vger.kernel.org \
    /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).