Linux RDMA and InfiniBand development
 help / color / mirror / Atom feed
From: Leon Romanovsky <leon@kernel.org>
To: bvanassche@acm.org, jgg@ziepe.ca,
	 Sara Venkatesh <sarajvenkatesh@gmail.com>
Cc: dledford@redhat.com, linux-rdma@vger.kernel.org,
	 target-devel@vger.kernel.org, linux-kernel@vger.kernel.org,
	 carlos.bilbao@kernel.org
Subject: Re: [PATCH] RDMA/srpt: fix integer overflow in immediate data length check
Date: Tue, 12 May 2026 06:41:28 -0400	[thread overview]
Message-ID: <177858248804.2277752.12077743618929897915.b4-ty@kernel.org> (raw)
In-Reply-To: <20260504080036.3482415-1-sarajvenkatesh@gmail.com>


On Mon, 04 May 2026 01:00:36 -0700, Sara Venkatesh wrote:
> imm_buf->len is a user-controlled uint32_t received from the network.
> Adding it to imm_data_offset without overflow checking allows a
> malicious initiator to send len=0xFFFFFFFF, causing req_size to wrap
> around to a small value, bypassing the bounds check, and subsequently
> passing a ~4GB length to sg_init_one().
> 
> Use check_add_overflow() to detect wrapping before the comparison.
> 
> [...]

Applied, thanks!

[1/1] RDMA/srpt: fix integer overflow in immediate data length check
      https://git.kernel.org/rdma/rdma/c/3f716b34c639f6

Best regards,
-- 
Leon Romanovsky <leon@kernel.org>


      parent reply	other threads:[~2026-05-12 10:41 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-04  8:00 [PATCH] RDMA/srpt: fix integer overflow in immediate data length check Sara Venkatesh
2026-05-04  8:17 ` Bart Van Assche
2026-05-05  0:11   ` Sara Venkatesh
2026-05-05  8:19 ` Bart Van Assche
2026-05-12 10:41 ` 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=177858248804.2277752.12077743618929897915.b4-ty@kernel.org \
    --to=leon@kernel.org \
    --cc=bvanassche@acm.org \
    --cc=carlos.bilbao@kernel.org \
    --cc=dledford@redhat.com \
    --cc=jgg@ziepe.ca \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rdma@vger.kernel.org \
    --cc=sarajvenkatesh@gmail.com \
    --cc=target-devel@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