[PATCH 2/5] nvmet: zns: don't leak stale memory in zone management receive

[Christoph Hellwig]

On Wed, Oct 14, 2026 at 01:00:00PM +0200, Andrea Parri wrote:
> On Tue, Oct 13, 2026 at 04:25:54PM +0200, Christoph Hellwig wrote:
> > On Mon, Oct 12, 2026 at 04:12:29PM +0200, Andrea Parri wrote:
> > > Tested over the loop, tcp, rdma and fc transports with a zoned
> > > null_blk namespace: before this patch, zone reports carried stale bytes
> > > and a data length larger than NUMD was accepted; with it, reports are
> > > fully initialized and such a length fails with Data SGL Length Invalid.
> > 
> > Can you wire up the reproduce in blktests?
> 
> Sure.  Following Documentation/process/security-bugs.rst I had only
> offered the reproducers on request; since you'd like them in blktests,
> I'll post them to linux-block shortly, unless you'd rather have them
> off-list until the fixes are merged.  One test covers this patch, and
> two more cover the fc and NUMD patches of this series.

I would not consider anything relating nvme except for userspace API
a security issue.  The protocols are clearly not designed for and/or
advertised for untrusted networks.

Just to make it clear, that's not to say we don't want these fixed,
but they are considered robustness fixes and not security issues.