public inbox for linux-rdma@vger.kernel.org
 help / color / mirror / Atom feed
From: Leon Romanovsky <leon@kernel.org>
To: Shiraz Saleem <shiraz.saleem@intel.com>
Cc: jgg@nvidia.com, linux-rdma@vger.kernel.org,
	ivan.d.barrera@intel.com,
	Christopher Bednarz <christopher.n.bednarz@intel.com>
Subject: Re: [PATCH for-rc] RDMA/irdma: Prevent zero-length STAG registration
Date: Sat, 19 Aug 2023 19:29:24 +0300	[thread overview]
Message-ID: <20230819162924.GR22185@unreal> (raw)
In-Reply-To: <20230818144838.1758-1-shiraz.saleem@intel.com>

On Fri, Aug 18, 2023 at 09:48:38AM -0500, Shiraz Saleem wrote:
> From: Christopher Bednarz <christopher.n.bednarz@intel.com>
> 
> Currently irdma allows zero-length STAGs to be programmed in HW during
> the kernel mode fast register flow. Zero-length MR or STAG registration
> disable HW memory length checks.
> 
> Improve gaps in bounds checking in irdma by preventing zero-length STAG or
> MR registrations except if the IB_PD_UNSAFE_GLOBAL_RKEY is set.
> 
> This addresses the disclosure CVE-2023-25775.
> 
> Fixes: b48c24c2d710 ("RDMA/irdma: Implement device supported verb APIs")
> Signed-off-by: Christopher Bednarz <christopher.n.bednarz@intel.com>
> Signed-off-by: Shiraz Saleem <shiraz.saleem@intel.com>
> ---
>  drivers/infiniband/hw/irdma/ctrl.c  |  6 ++++++
>  drivers/infiniband/hw/irdma/type.h  |  2 ++
>  drivers/infiniband/hw/irdma/verbs.c | 10 ++++++++--
>  3 files changed, 16 insertions(+), 2 deletions(-)

I applied it to rdma-next because we are in -rc6 now and anyway this
patch will land Linus very soon.

Thanks

  reply	other threads:[~2023-08-19 16:29 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-18 14:48 [PATCH for-rc] RDMA/irdma: Prevent zero-length STAG registration Shiraz Saleem
2023-08-19 16:29 ` Leon Romanovsky [this message]
2023-08-21  7:41 ` Leon Romanovsky
2023-09-05  4:07 ` liujian (CE)
2023-09-15 17:34   ` Saleem, Shiraz

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=20230819162924.GR22185@unreal \
    --to=leon@kernel.org \
    --cc=christopher.n.bednarz@intel.com \
    --cc=ivan.d.barrera@intel.com \
    --cc=jgg@nvidia.com \
    --cc=linux-rdma@vger.kernel.org \
    --cc=shiraz.saleem@intel.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