From: Leon Romanovsky <leon@kernel.org>
To: yanjun.zhu@linux.dev, zyjzyj2000@gmail.com, jgg@ziepe.ca,
Ibrahim Hashimov <security@auditcode.ai>
Cc: linux-rdma@vger.kernel.org, linux-kernel@vger.kernel.org,
stable@vger.kernel.org
Subject: Re: [PATCH v3] RDMA/rxe: fix responder UAF on IB_QP_MAX_DEST_RD_ATOMIC modify_qp
Date: Thu, 16 Jul 2026 04:14:45 -0400 [thread overview]
Message-ID: <178418968562.292019.4878349763423795235.b4-ty@kernel.org> (raw)
In-Reply-To: <20260712121720.78001-1-security@auditcode.ai>
On Sun, 12 Jul 2026 14:17:20 +0200, Ibrahim Hashimov wrote:
> rxe_qp_from_attr() handles IB_QP_MAX_DEST_RD_ATOMIC outside the
> IB_QP_STATE path, so it holds no state_lock and runs while the responder
> task rxe_receiver() (recv_task on rxe_wq) is live. A modify_qp() setting
> only that attribute calls free_rd_atomic_resources() then
> alloc_rd_atomic_resources(), swapping qp->resp.resources[] while
> rxe_prepare_res()/find_resource() walk it; free_rd_atomic_resources()
> also leaves the cached pointer qp->resp.res dangling. A local
> unprivileged user can race the free/realloc into a use-after-free in
> rxe_receiver() (local DoS).
>
> [...]
Applied, thanks!
[1/1] RDMA/rxe: fix responder UAF on IB_QP_MAX_DEST_RD_ATOMIC modify_qp
https://git.kernel.org/rdma/rdma/c/a37da605b395b9
Best regards,
--
Leon Romanovsky <leon@kernel.org>
prev parent reply other threads:[~2026-07-16 8:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-12 12:17 [PATCH v3] RDMA/rxe: fix responder UAF on IB_QP_MAX_DEST_RD_ATOMIC modify_qp Ibrahim Hashimov
2026-07-16 8:14 ` Leon Romanovsky [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=178418968562.292019.4878349763423795235.b4-ty@kernel.org \
--to=leon@kernel.org \
--cc=jgg@ziepe.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=security@auditcode.ai \
--cc=stable@vger.kernel.org \
--cc=yanjun.zhu@linux.dev \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox