From: Leon Romanovsky <leon@kernel.org>
To: yunje shin <yjshin0438@gmail.com>
Cc: jgg@ziepe.ca, ioerts@kookmin.ac.kr, joonkyoj@yonsei.ac.kr,
linux-rdma@vger.kernel.org
Subject: Re: [PATCH v2] RDMA/umad: Reject negative data_len in ib_umad_write
Date: Sun, 8 Feb 2026 08:53:28 +0200 [thread overview]
Message-ID: <20260208065328.GA12887@unreal> (raw)
In-Reply-To: <CAMX6_QFeVW=ZgyLT_07GeEbn443osvaPa6XUWFeqztFRmfUEmg@mail.gmail.com>
On Sun, Feb 08, 2026 at 03:00:41PM +0900, yunje shin wrote:
> I noticed I missed the Cc: stable tag. Should this fix be backported
> to stable trees as well?
1. We (the RDMA maintainers) almost always remove stable@ tags from
submitted patches. We prefer to reserve those tags for cases that
truly warrant them, where we can take the extra step of preparing a
proper backport.
2. Patches that include a Fixes line are automatically considered for
stable@ inclusion by the AUTOSEL tool used by the stable maintainers.
Thanks
>
> Thanks, YunJe Shin
>
> On Thu, Feb 5, 2026 at 9:53 PM Leon Romanovsky <leon@kernel.org> wrote:
> >
> >
> > On Tue, 03 Feb 2026 19:06:21 +0900, YunJe Shin wrote:
> > > ib_umad_write computes data_len from user-controlled count and the
> > > MAD header sizes. With a mismatched user MAD header size and RMPP
> > > header length, data_len can become negative and reach ib_create_send_mad().
> > > This can make the padding calculation exceed the segment size and trigger
> > > an out-of-bounds memset in alloc_send_rmpp_list().
> > >
> > > Add an explicit check to reject negative data_len before creating the
> > > send buffer.
> > >
> > > [...]
> >
> > Applied, thanks!
> >
> > [1/1] RDMA/umad: Reject negative data_len in ib_umad_write
> > https://git.kernel.org/rdma/rdma/c/5551b02fdbfd85
> >
> > Best regards,
> > --
> > Leon Romanovsky <leon@kernel.org>
> >
>
prev parent reply other threads:[~2026-02-08 6:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-03 10:06 [PATCH v2] RDMA/umad: Reject negative data_len in ib_umad_write YunJe Shin
2026-02-05 12:53 ` Leon Romanovsky
2026-02-08 6:00 ` yunje shin
2026-02-08 6:53 ` 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=20260208065328.GA12887@unreal \
--to=leon@kernel.org \
--cc=ioerts@kookmin.ac.kr \
--cc=jgg@ziepe.ca \
--cc=joonkyoj@yonsei.ac.kr \
--cc=linux-rdma@vger.kernel.org \
--cc=yjshin0438@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