From: Zhu Yanjun <yanjun.zhu@linux.dev>
To: Norbert Szetei <norbert@doyensec.com>,
linux-rdma@vger.kernel.org,
"yanjun.zhu@linux.dev" <yanjun.zhu@linux.dev>
Cc: Zhu Yanjun <zyjzyj2000@gmail.com>, Jason Gunthorpe <jgg@ziepe.ca>,
Leon Romanovsky <leon@kernel.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] RDMA/rxe: validate access flags before swapping the MR's PD
Date: Thu, 27 Aug 2026 15:26:07 -0700 [thread overview]
Message-ID: <dc993a28-cc91-4674-a52f-511e8bb54876@linux.dev> (raw)
In-Reply-To: <46E1D5C0-24BE-4D01-BDB3-634FE09B22C5@doyensec.com>
在 2026/8/27 10:18, Norbert Szetei 写道:
> rxe_rereg_user_mr() reassigns mr->ibmr.pd first and only then
> validates the IB_MR_REREG_ACCESS argument:
>
> if (flags & IB_MR_REREG_PD) {
> rxe_put(old_pd);
> rxe_get(pd);
> mr->ibmr.pd = ibpd;
> }
>
> if (flags & IB_MR_REREG_ACCESS) {
> if (access & ~RXE_ACCESS_SUPPORTED_MR)
> return ERR_PTR(-EOPNOTSUPP);
> mr->access = access;
> }
>
> Both flags pass the entry check because RXE_MR_REREG_SUPPORTED is
> IB_MR_REREG_PD | IB_MR_REREG_ACCESS, so a caller can reach the access
> check with mr->ibmr.pd already reassigned.
>
> mr->ibmr.pd is owned by the core, which adjusts pd->usecnt only on the
> success path: ib_uverbs_rereg_mr() jumps to put_new_uobj on a driver error
> without undoing the reassignment, so mr->pd == new_pd while the usecnts
> still charge the MR to orig_pd. ib_dereg_mr_user() then decrements
> new_pd, whose count can reach zero while a memory window still references
> it; uverbs_free_pd() frees the PD on that count alone and rxe_mw_cleanup()
> writes to freed memory:
>
> BUG: KASAN: slab-use-after-free in __rxe_put+0x31/0xa0
> Write of size 4 at addr ffff8881301dd690 by task rxe_poc/591
> __rxe_put+0x31/0xa0
> rxe_mw_cleanup+0x42/0x200
> __rxe_cleanup+0x115/0x370
> rxe_dealloc_mw+0x4c/0x80
> Allocated by task 591:
> ib_uverbs_alloc_pd+0x258/0x540
> Freed by task 591:
> ib_dealloc_pd_user+0x174/0x210
> uverbs_free_pd+0x8d/0xc0
> ib_uverbs_dealloc_pd+0x18e/0x1d0
>
> Validate the access flags before mutating any state so the callback either
> applies every requested change or none.
>
> Fixes: 544c7f62cf32 ("RDMA/rxe: Implement rereg_user_mr")> Cc: stable@vger.kernel.org
> Signed-off-by: Norbert Szetei <norbert@doyensec.com>
Thanks a lot. I am fine with this commit.
Reviewed-by: Zhu Yanjun <yanjun.zhu@linux.dev>
Zhu Yanjun
> ---
> drivers/infiniband/sw/rxe/rxe_verbs.c | 13 +++++++------
> 1 file changed, 7 insertions(+), 6 deletions(-)
>
> diff --git a/drivers/infiniband/sw/rxe/rxe_verbs.c b/drivers/infiniband/sw/rxe/rxe_verbs.c
> index 96c7716057fe..3864284522eb 100644
> --- a/drivers/infiniband/sw/rxe/rxe_verbs.c
> +++ b/drivers/infiniband/sw/rxe/rxe_verbs.c
> @@ -1331,19 +1331,20 @@ static struct ib_mr *rxe_rereg_user_mr(struct ib_mr *ibmr, int flags,
> if (err)
> return ERR_PTR(err);
>
> + if ((flags & IB_MR_REREG_ACCESS) &&
> + (access & ~RXE_ACCESS_SUPPORTED_MR)) {
> + rxe_err_mr(mr, "access = %#x not supported\n", access);
> + return ERR_PTR(-EOPNOTSUPP);
> + }
> +
> if (flags & IB_MR_REREG_PD) {
> rxe_put(old_pd);
> rxe_get(pd);
> mr->ibmr.pd = ibpd;
> }
>
> - if (flags & IB_MR_REREG_ACCESS) {
> - if (access & ~RXE_ACCESS_SUPPORTED_MR) {
> - rxe_err_mr(mr, "access = %#x not supported\n", access);
> - return ERR_PTR(-EOPNOTSUPP);
> - }
> + if (flags & IB_MR_REREG_ACCESS)
> mr->access = access;
> - }
>
> return NULL;
> }
next prev parent reply other threads:[~2026-08-27 22:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-27 17:18 [PATCH] RDMA/rxe: validate access flags before swapping the MR's PD Norbert Szetei
2026-08-27 22:26 ` Zhu Yanjun [this message]
2026-09-01 10:07 ` 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=dc993a28-cc91-4674-a52f-511e8bb54876@linux.dev \
--to=yanjun.zhu@linux.dev \
--cc=jgg@ziepe.ca \
--cc=leon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=norbert@doyensec.com \
--cc=zyjzyj2000@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.