From: Chris Leech <cleech@redhat.com>
To: Ratnaker Gautam <ratnaker.gautam@kuleuven.be>
Cc: "linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
"lduncan@suse.com" <lduncan@suse.com>,
"michael.christie@oracle.com" <michael.christie@oracle.com>,
James Bottomley <james.bottomley@hansenpartnership.com>,
"mkp@kernel.org" <mkp@kernel.org>
Subject: Re: [PATCH] scsi: libiscsi_tcp: prevent R2T range check overflow
Date: Mon, 19 Oct 2026 20:38:27 -0700 [thread overview]
Message-ID: <20261019-purging-charm-a883db232701@redhat.com> (raw)
In-Reply-To: <DB5PR08MB100629CD3750FBF71475B5224FD982@DB5PR08MB10062.eurprd08.prod.outlook.com>
On Mon, Oct 19, 2026 at 09:30:33PM +0000, Ratnaker Gautam wrote:
> An iSCSI target controls the R2T data offset and length as 32-bit
> values. Adding them before comparing the result with the SCSI data
> buffer length can wrap. An R2T with offset 1 and length U32_MAX then
> passes the check for a 4096-byte write.
>
> The transmit path treats the wrapped range as valid, exhausts the
> command scatterlist, and dereferences the NULL next entry in
> iscsi_tcp_segment_done().
>
> Check the offset first, then compare the length with the remaining
> bytes in the data buffer.
>
> Fixes: a081c13e39b5 ("[SCSI] iscsi_tcp: split module into lib and lld")
> Cc: stable@vger.kernel.org
> Signed-off-by: Ratnaker Gautam <ratnaker.gautam@kuleuven.be>
> ---
> drivers/scsi/libiscsi_tcp.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/scsi/libiscsi_tcp.c b/drivers/scsi/libiscsi_tcp.c
> index d35f93451ee9b..3c9e736d45e7e 100644
> --- a/drivers/scsi/libiscsi_tcp.c
> +++ b/drivers/scsi/libiscsi_tcp.c
> @@ -601,7 +601,8 @@ static int iscsi_tcp_r2t_rsp(struct iscsi_conn *conn, struct iscsi_hdr *hdr)
> data_length, session->max_burst);
>
> data_offset = be32_to_cpu(rhdr->data_offset);
> - if (data_offset + data_length > task->sc->sdb.length) {
> + if (data_offset > task->sc->sdb.length ||
> + data_length > task->sc->sdb.length - data_offset) {
> iscsi_conn_printk(KERN_ERR, conn,
> "invalid R2T with data len %u at offset %u "
> "and total length %d\n", data_length,
> --
Acked-by: Chris Leech <cleech@redhat.com>
next prev parent reply other threads:[~2026-10-20 3:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-19 21:30 [PATCH] scsi: libiscsi_tcp: prevent R2T range check overflow Ratnaker Gautam
2026-10-20 3:38 ` Chris Leech [this message]
2026-10-24 2:48 ` Martin K. Petersen
2026-10-29 2:02 ` Martin K. Petersen (Oracle)
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=20261019-purging-charm-a883db232701@redhat.com \
--to=cleech@redhat.com \
--cc=james.bottomley@hansenpartnership.com \
--cc=lduncan@suse.com \
--cc=linux-scsi@vger.kernel.org \
--cc=michael.christie@oracle.com \
--cc=mkp@kernel.org \
--cc=ratnaker.gautam@kuleuven.be \
/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