From: Leon Romanovsky <leon@kernel.org>
To: Haitam Lazaar <haitam@lazaarsec.com>
Cc: Bernard Metzler <bernard.metzler@linux.dev>,
Jason Gunthorpe <jgg@ziepe.ca>,
linux-rdma <linux-rdma@vger.kernel.org>,
stable <stable@vger.kernel.org>
Subject: Re: [PATCH for-rc] RDMA/siw: Enforce IB_ACCESS_REMOTE_READ for read responses
Date: Sun, 11 Oct 2026 13:53:41 +0300 [thread overview]
Message-ID: <20261011105341.GC27033@unreal> (raw)
In-Reply-To: <1a109695301.353d00802169.3051945239243282542@lazaarsec.com>
On Mon, Oct 05, 2026 at 12:14:19AM +0000, Haitam Lazaar wrote:
> When generating an RDMA READ response (SIW_OP_READ_RESPONSE),
>
> siw_check_sgl_tx() unconditionally passes 0 as the required permission
>
> mask:
>
>
>
> /* Reference memory to be tx'd w/o checking access for LOCAL_READ */
>
> rv = siw_check_sgl_tx(qp->pd, wqe, 0);
>
>
>
> Because perms is 0, siw_check_mem()'s authorization test:
>
> if ((mem->perms & perms) < perms)
>
> evaluates to (mem->perms & 0) < 0, which is always false. Consequently,
>
> an untrusted remote peer can issue an RDMA Read targeting any valid
>
> STag in the Protection Domain, even if the memory was registered strictly
>
> as write-only (IB_ACCESS_REMOTE_WRITE) without IB_ACCESS_REMOTE_READ.
>
>
>
> Enforce that the target memory region was granted IB_ACCESS_REMOTE_READ
>
> when answering SIW_OP_READ_RESPONSE work queue entries, while preserving
>
> perms = 0 for standard local sends.
>
>
>
> Fixes: b9be6f18cf9e ("rdma/siw: transmit path")
>
> Cc: mailto:stable@vger.kernel.org
Please read Documentation/process/email-clients.rst, remove stable and
resend the patch.
Thanks
>
> Signed-off-by: Haitam Lazaar < mailto:haitam@lazaarsec.com >
>
> ---
>
> drivers/infiniband/sw/siw/siw_qp_tx.c | 13 +++++++++----
>
> 1 file changed, 9 insertions(+), 4 deletions(-)
>
>
>
> diff --git a/drivers/infiniband/sw/siw/siw_qp_tx.c b/drivers/infiniband/sw/siw/siw_qp_tx.c
>
> index f7dd32c6e5ba..9e652585f904 100644
>
> --- a/drivers/infiniband/sw/siw/siw_qp_tx.c
>
> +++ b/drivers/infiniband/sw/siw/siw_qp_tx.c
>
> @@ -810,12 +810,17 @@ static int siw_qp_sq_proc_tx(struct siw_qp *qp, struct siw_wqe *wqe)
>
>
>
> if (tx_type(wqe) != SIW_OP_READ &&
>
> tx_type(wqe) != SIW_OP_READ_LOCAL_INV) {
>
> + enum ib_access_flags perms = 0;
>
> +
>
> /*
>
> - * Reference memory to be tx'd w/o checking
>
> - * access for LOCAL_READ permission, since
>
> - * not defined in RDMA core.
>
> + * Local READ permission doesn't exist in RDMA core.
>
> + * A READ RESPONSE source is read by the remote peer,
>
> + * so it must be checked for REMOTE_READ permission.
>
> */
>
> - rv = siw_check_sgl_tx(qp->pd, wqe, 0);
>
> + if (tx_type(wqe) == SIW_OP_READ_RESPONSE)
>
> + perms = IB_ACCESS_REMOTE_READ;
>
> +
>
> + rv = siw_check_sgl_tx(qp->pd, wqe, perms);
>
> if (rv < 0) {
>
> if (tx_type(wqe) ==
>
> SIW_OP_READ_RESPONSE)
>
> --
next parent reply other threads:[~2026-10-11 10:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1a109695301.353d00802169.3051945239243282542@lazaarsec.com>
2026-10-11 10:53 ` Leon Romanovsky [this message]
2026-10-05 0:25 [PATCH for-rc] RDMA/siw: Enforce IB_ACCESS_REMOTE_READ for read responses Haitam Lazaar
2026-10-05 0:35 ` sashiko-bot
2026-10-05 11:31 ` Bernard Metzler
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=20261011105341.GC27033@unreal \
--to=leon@kernel.org \
--cc=bernard.metzler@linux.dev \
--cc=haitam@lazaarsec.com \
--cc=jgg@ziepe.ca \
--cc=linux-rdma@vger.kernel.org \
--cc=stable@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