diff options
| author | Bryam Vargas <hexlabsecurity@proton.me> | 2026-07-02 03:45:14 -0500 |
|---|---|---|
| committer | Keith Busch <kbusch@kernel.org> | 2026-07-06 11:39:52 -0700 |
| commit | 3ddcfb013322aa37eaa7a0d344b73079c38dfa21 (patch) | |
| tree | cfe7060c43acc21479f3111dbe79a5614b45eb8b /tools/perf/scripts/python/bin/stackcollapse-record | |
| parent | 3a6d89836ab09d53f4c32c57588689a378ce4363 (diff) | |
nvmet-auth: zero the AUTH_RECEIVE response buffer
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.
Fixes: db1312dd9548 ("nvmet: implement basic In-Band Authentication")
Cc: stable@vger.kernel.org
Signed-off-by: Bryam Vargas <hexlabsecurity@proton.me>
Reviewed-by: Christoph Hellwig <hch@lst.de>
Signed-off-by: Keith Busch <kbusch@kernel.org>
Diffstat (limited to 'tools/perf/scripts/python/bin/stackcollapse-record')
0 files changed, 0 insertions, 0 deletions
