Re: [PATCH] nvmet-auth: zero the AUTH_RECEIVE response buffer
Keith Busch <[email protected]>
| Newsgroups | org.infradead.lists.linux-nvme,org.kernel.vger.linux-kernel |
|---|---|
| Message-ID | <akv6siYknndH0Cr-@kbusch-mbp> |
On Thu, Jul 02, 2026 at 03:45:14AM -0500, Bryam Vargas via B4 Relay wrote: > From: Bryam Vargas <[email protected]> > > nvmet_execute_auth_receive() allocates the response buffer with kmalloc() > sized by the host-supplied AUTH_RECEIVE allocation length, but the > DH-HMAC-CHAP builders write only a fixed-size message into it. The full > allocation length is then copied to the wire by nvmet_copy_to_sgl(), so a > remote initiator receives the bytes past the built message -- up to nearly > a page of uninitialized slab -- during the pre-authentication handshake. > > Allocate the buffer with kzalloc() so the unwritten tail is zeroed before > it is sent; conforming responses are unaffected. Thanks, applied to nvme-7.3.