Nixpkgs security tracker

Try the new UI
Login with GitHub
⚠️ You are using a production deployment that is still only suitable for demo purposes. Any work done in this might be wiped later without notice.

Suggestion detail

Dismissed
(max. allowed matches exceeded)
created 1 week, 6 days ago Activity log
  • Created & dismissed (max. allowed matches exceeded) suggestion
nvmet-auth: zero the AUTH_RECEIVE response buffer

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.

Affected products

Linux
  • <3ddcfb013322aa37eaa7a0d344b73079c38dfa21
  • =<7.1.*
  • <2dcc9226203da7275a9c29d20007da278d73d5e9
  • <1d6837d98bf966a041af65de5f78de7409ff83bc
  • =<7.2.*
  • =<6.1.*
  • =<*
  • <dfcf013f77709ebdb282767edc2795a37cab5b57
  • <8f6363c8d54dde95982f0ab45e77cf57ec0efd62
  • <447b668faa14710f611e714031e3739ac3ec3a4f
  • <6.0
  • =<6.18.*
  • =<6.12.*
  • <b26189d28442183a8b5edb754f4a6918f77ca84e
  • =<6.6.*
  • ==6.0