Linux RDMA and InfiniBand development
 help / color / mirror / Atom feed
From: Jason Gunthorpe <jgunthorpe@obsidianresearch.com>
To: "Ismail, Mustafa" <mustafa.ismail@intel.com>
Cc: Doug Ledford <dledford@redhat.com>,
	"linux-rdma@vger.kernel.org" <linux-rdma@vger.kernel.org>,
	"stable@vger.kernel.org" <stable@vger.kernel.org>,
	"security@kernel.org" <security@kernel.org>,
	Yevgeny Kliteynik <kliteyn@mellanox.com>,
	Tziporet Koren <tziporet@mellanox.com>,
	Alex Polak <alexpo@mellanox.com>,
	Boris Pismenny <borisp@mellanox.com>,
	Leon Romanovsky <leon@kernel.org>
Subject: Re: [PATCH] RDMA/uverbs: Check port number supplied by user verbs cmds
Date: Tue, 11 Jul 2017 22:02:09 -0600	[thread overview]
Message-ID: <20170712040209.GA26073@obsidianresearch.com> (raw)
In-Reply-To: <5C5647B5F4794941BAAC07CF28785CBC33E4CB61@fmsmsx101.amr.corp.intel.com>

On Tue, Jul 11, 2017 at 11:21:07PM +0000, Ismail, Mustafa wrote:
> > Subject: [PATCH] RDMA/uverbs: Check port number supplied by user verbs
> > cmds
> > 
> > Upstream commit id in the rdma.git tree: 5ecce4c9b17b
> > 
> > The ib_uverbs_create_ah() ind ib_uverbs_modify_qp() calls receive the port
> > number from user input as part of its attributes and assumes it is valid.
> > Down on the stack, that parameter is used to access kernel data structures.
> > If the value is invalid, the kernel accesses memory it should not.  To prevent
> > this, verify the port number before using it.
> > 
> > BUG: KASAN: use-after-free in ib_uverbs_create_ah+0x6d5/0x7b0 Read of
> > size 4 at addr ffff880018d67ab8 by task syz-executor/313
> > 
> > BUG: KASAN: slab-out-of-bounds in modify_qp.isra.4+0x19d0/0x1ef0 Read
> > of size 4 at addr ffff88006c40ec58 by task syz-executor/819
> > 
> > Fixes: 67cdb40ca444 ("[IB] uverbs: Implement more commands")
> > Cc: <stable@vger.kernel.org> # v4.2-v4.9
> > Cc: <security@kernel.org>
> > Cc: Yevgeny Kliteynik <kliteyn@mellanox.com>
> > Cc: Tziporet Koren <tziporet@mellanox.com>
> > Cc: Alex Polak <alexpo@mellanox.com>
> > Signed-off-by: Boris Pismenny <borisp@mellanox.com>
> > Signed-off-by: Leon Romanovsky <leon@kernel.org>
> > Signed-off-by: Doug Ledford <dledford@redhat.com>
> > 
> > Modified from upstream commit: helper function rdma_is_port_valid does
> > not exist in these kernel versions, so use manual comparisons instead.
> > 
> >  drivers/infiniband/core/uverbs_cmd.c | 8 ++++++++
> >  1 file changed, 8 insertions(+)
> > 
> > diff --git a/drivers/infiniband/core/uverbs_cmd.c
> > b/drivers/infiniband/core/uverbs_cmd.c
> > index cb3f515a2285..01e3a37b0aef 100644
> > +++ b/drivers/infiniband/core/uverbs_cmd.c
> > @@ -2342,6 +2342,10 @@ ssize_t ib_uverbs_modify_qp(struct
> > ib_uverbs_file *file,
> >  	if (copy_from_user(&cmd, buf, sizeof cmd))
> >  		return -EFAULT;
> > 
> > +	if (cmd.port_num < rdma_start_port(ib_dev) ||
> > +	    cmd.port_num > rdma_end_port(ib_dev))
> > +		return -EINVAL;
> > +
> With this check for valid port number, ucma_modify_qp_sqd() and ucma_modify_qp_err () in rdma-core may fail since qp_attr.port_num is not initialized.

Indeed. port_num should be totally ignored if not present in
attr_mask, and should not trigger EINVAL.

Jason

      reply	other threads:[~2017-07-12  4:02 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-07 15:36 [PATCH] RDMA/uverbs: Check port number supplied by user verbs cmds Doug Ledford
2017-07-08 14:04 ` Leon Romanovsky
     [not found] ` <23a56bbd03a2b5b585e2de35b1fc6f8bac53aa9a.1499441641.git.dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2017-07-11 23:21   ` Ismail, Mustafa
2017-07-12  4:02     ` Jason Gunthorpe [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=20170712040209.GA26073@obsidianresearch.com \
    --to=jgunthorpe@obsidianresearch.com \
    --cc=alexpo@mellanox.com \
    --cc=borisp@mellanox.com \
    --cc=dledford@redhat.com \
    --cc=kliteyn@mellanox.com \
    --cc=leon@kernel.org \
    --cc=linux-rdma@vger.kernel.org \
    --cc=mustafa.ismail@intel.com \
    --cc=security@kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=tziporet@mellanox.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