From: "Saleem, Shiraz" <shiraz.saleem@intel.com>
To: "lyl2019@mail.ustc.edu.cn" <lyl2019@mail.ustc.edu.cn>
Cc: Jason Gunthorpe <jgg@nvidia.com>,
"Latif, Faisal" <faisal.latif@intel.com>,
"dledford@redhat.com" <dledford@redhat.com>,
"linux-rdma@vger.kernel.org" <linux-rdma@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: RE: RE: [PATCH] infiniband/i40iw: Fix a use after free in i40iw_cm_event_handler
Date: Sat, 13 Mar 2021 01:11:42 +0000 [thread overview]
Message-ID: <eba3dbe9bf734dc0b65b2e65aa8d5bd9@intel.com> (raw)
In-Reply-To: <43271428.d966.1782426e7a3.Coremail.lyl2019@mail.ustc.edu.cn>
> Subject: Re: RE: [PATCH] infiniband/i40iw: Fix a use after free in
> i40iw_cm_event_handler
>
>
>
>
> > -----原始邮件-----
> > 发件人: "Saleem, Shiraz" <shiraz.saleem@intel.com>
> > 发送时间: 2021-03-12 09:13:39 (星期五)
> > 收件人: "Jason Gunthorpe" <jgg@nvidia.com>, "Lv Yunlong"
> > <lyl2019@mail.ustc.edu.cn>
> > 抄送: "Latif, Faisal" <faisal.latif@intel.com>, "dledford@redhat.com"
> > <dledford@redhat.com>, "linux-rdma@vger.kernel.org"
> > <linux-rdma@vger.kernel.org>, "linux-kernel@vger.kernel.org"
> > <linux-kernel@vger.kernel.org>
> > 主题: RE: [PATCH] infiniband/i40iw: Fix a use after free in
> > i40iw_cm_event_handler
> >
> > > Subject: Re: [PATCH] infiniband/i40iw: Fix a use after free in
> > > i40iw_cm_event_handler
> > >
> > > On Wed, Mar 10, 2021 at 07:14:14PM -0800, Lv Yunlong wrote:
> > > > In the case of I40IW_CM_EVENT_ABORTED, i40iw_event_connect_error()
> > > > could be called to free the event->cm_node. However,
> > > > event->cm_node will be used after and cause use after free. It
> > > > needs to add flags to inform that event->cm_node has been freed.
> > > >
> > > > Signed-off-by: Lv Yunlong <lyl2019@mail.ustc.edu.cn>
> > > > ---
> > > > drivers/infiniband/hw/i40iw/i40iw_cm.c | 5 ++++-
> > > > 1 file changed, 4 insertions(+), 1 deletion(-)
> > >
> > > This might be OK (though I don't like the free variable), Shiraz??
> > >
> >
> > How was this reproduced? Do you have some call trace leading up to use after
> free?
> >
> > The cm_node refcnt is bumped at creation time and once in i40iw_receive_ilq
> before packet is processed.
> > That should protect the cm_node from disappearing in the event handler in the
> abort event case.
> > The dec at end of i40iw_receive ilq should be point where the cm_node is freed
> specifically in the abort case.
> >
> > Shiraz
> >
>
> This problem was reported by a path-sensitive analyzer developed by our Security
> Lab(Loccs).
> The analyzer reported that there is a feasible path to free event->cm_node and use
> it after, and that is what i described in the first commit.
>
OK. I don’t think that an extra dec refcnt in itself for the abort case is enough evidence to
say that the cm_node is freed in i40iw_event_connect_error.
Shiraz
prev parent reply other threads:[~2021-03-13 1:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-11 3:14 [PATCH] infiniband/i40iw: Fix a use after free in i40iw_cm_event_handler Lv Yunlong
2021-03-11 18:21 ` Jason Gunthorpe
2021-03-12 1:13 ` Saleem, Shiraz
2021-03-12 1:57 ` lyl2019
2021-03-13 1:11 ` Saleem, Shiraz [this message]
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=eba3dbe9bf734dc0b65b2e65aa8d5bd9@intel.com \
--to=shiraz.saleem@intel.com \
--cc=dledford@redhat.com \
--cc=faisal.latif@intel.com \
--cc=jgg@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=lyl2019@mail.ustc.edu.cn \
/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