From: "Maurizio Lombardi" <mlombard@arkamax.eu>
To: "Shivam Kumar" <kumar.shivam43666@gmail.com>,
<linux-nvme@lists.infradead.org>
Cc: "Sagi Grimberg" <sagi@grimberg.me>,
"Keith Busch" <kbusch@kernel.org>,
"Ibrahim Hashimov" <security@auditcode.ai>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>
Subject: Re: Prior report for the nvmet-tcp unbounded SGL length fix in 7.3
Date: Mon, 24 Aug 2026 18:31:15 +0200 [thread overview]
Message-ID: <DKXBFWLKS911.MABX0LKENDSF@arkamax.eu> (raw)
In-Reply-To: <CA+ysrSKO9ufMWQ=s_xM_uh1OhKmEb8v0tOwYH+g2vtxeWqW8DQ@mail.gmail.com>
On Mon Aug 24, 2026 at 5:42 PM CEST, Shivam Kumar wrote:
> Hi all,
>
> I originally reported this issue to security@kernel.org on 2026-03-17
> (Cc Sagi), Message-ID:
> <CA+ysrSJUFi8cHzU8g9Nrbbkcuo0F7vh8CMn3ht15gSk3BbK45A@mail.gmail.com>
> and posted the first patch for it in this thread,
> "[PATCH] nvmet-tcp: bound sgl->length check in nvmet_tcp_map_data()"
> (2026-03-19).
>
> Commit 4a3f002 ("nvmet-tcp: bound SGL data length before allocating
> command buffers"), merged for 7.3, adds the same NVMET_TCP_MAXH2CDATA
> bound with the same status code.
I didn't notice this new patch, but I still suspect that MAXH2CDATA is misused
and that the correct solution is to set MDTS.
Maurizio
prev parent reply other threads:[~2026-08-24 16:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-24 15:42 Prior report for the nvmet-tcp unbounded SGL length fix in 7.3 Shivam Kumar
2026-08-24 15:50 ` Shivam Kumar
2026-08-24 16:01 ` Greg Kroah-Hartman
2026-08-24 16:07 ` Shivam Kumar
2026-08-24 16:54 ` Greg Kroah-Hartman
2026-08-24 18:18 ` Shivam Kumar
2026-08-25 8:13 ` Greg Kroah-Hartman
2026-08-24 16:31 ` Maurizio Lombardi [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=DKXBFWLKS911.MABX0LKENDSF@arkamax.eu \
--to=mlombard@arkamax.eu \
--cc=gregkh@linuxfoundation.org \
--cc=kbusch@kernel.org \
--cc=kumar.shivam43666@gmail.com \
--cc=linux-nvme@lists.infradead.org \
--cc=sagi@grimberg.me \
--cc=security@auditcode.ai \
/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.