nvmet-auth: zero the AUTH_RECEIVE response buffer
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ db1312dd95488b5e6ff362ff66fcf953a46b1821 · < 1d6837d98bf966a041af65de5f78de7409ff83bc| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
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.
From the CVE record · Linux
The Linux kernel's nvmet-auth AUTH_RECEIVE response can include uninitialized memory because its buffer is not zeroed before the full allocation is sent. A remote initiator can receive those bytes during the pre-authentication handshake; no prior authentication or user interaction is required.
Operators running Linux kernels with the affected nvmet-auth implementation should check their installations; affected versions were not specified.