From: Sasha Levin <sashal@kernel.org>
To: stable@vger.kernel.org
Cc: Sasha Levin <sashal@kernel.org>,
Peiyang He <peiyang_he@smail.nju.edu.cn>,
Zhu Yanjun <yanjun.zhu@linux.dev>,
Leon Romanovsky <leonro@nvidia.com>
Subject: Re: [PATCH 7.2.y] RDMA/rxe: Fix OOB in free_rd_atomic_resources()
Date: Thu, 27 Aug 2026 01:17:53 -0400 [thread overview]
Message-ID: <20260827050834.10003.stable-daily@kernel.org> (raw)
In-Reply-To: <20260825163605.21809-1-yanjun.zhu@linux.dev>
> free_rd_atomic_resources() iterates using qp->attr.max_dest_rd_atomic.
> Updating max_dest_rd_atomic before freeing the old array can make the
> free path walk past the old allocation and trigger a slab out-of-bounds
> write catched by KASAN:
Queued for 7.2, 7.1, 6.18, 6.12 and 6.6, thanks.
--
Thanks,
Sasha
prev parent reply other threads:[~2026-08-27 5:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-25 11:04 FAILED: patch "[PATCH] RDMA/rxe: Fix OOB in free_rd_atomic_resources()" failed to apply to 7.2-stable tree gregkh
2026-08-25 14:47 ` Zhu Yanjun
2026-08-25 15:15 ` Greg KH
2026-08-25 16:36 ` [PATCH 7.2.y] RDMA/rxe: Fix OOB in free_rd_atomic_resources() Zhu Yanjun
2026-08-27 5:17 ` Sasha Levin [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=20260827050834.10003.stable-daily@kernel.org \
--to=sashal@kernel.org \
--cc=leonro@nvidia.com \
--cc=peiyang_he@smail.nju.edu.cn \
--cc=stable@vger.kernel.org \
--cc=yanjun.zhu@linux.dev \
/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.