Nixpkgs security tracker

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 3 weeks, 3 days ago Activity log
  • Created & dismissed (max. allowed matches exceeded) suggestion
rxrpc: rxrpc_verify_data ensure rx_dec_buffer alloc

In the Linux kernel, the following vulnerability has been resolved: rxrpc: rxrpc_verify_data ensure rx_dec_buffer alloc rxrpc_recvmsg_data() calls rxrpc_verify_data() whenever the rxrpc_call.rx_dec_buffer is unallocated and assumes that upon successful return that rx_dec_buffer must be allocated. However, rxrpc_verify_data() does not request an allocation if the rxrpc_skb_priv.len is zero. In addition, failure to allocate rx_dec_buffer will result in a call to skb_copy_bits() with a NULL destination which can trigger a NULL pointer dereference. To prevent these issues rxrpc_verify_data() is modified to always attempt to allocate the rxrpc_call.rx_dec_buffer if it is NULL. This issue was identified with assistance of a private sashiko instance.

Affected products

Linux
  • <7.1
  • ==c580087743712112778a06d65a4074053072d7bf
  • =<6.6.*
  • <7.1
  • =<*
  • <6.12.97
  • <8bbede0afced346b24e4fbde0c68cf12980ba948
  • <6.18.40
  • =<6.18.*
  • =<6.12.*
  • <6563b4eb38c35d75892445bcf8aacdc29914821c
  • =<7.1.*
  • ==7.1
  • <16c8ae9735c5bd7e54dd7478d6348e0fc860842d
  • <6.6.145
  • <d3b642cf95d48234590cc91450d8705a9bf6b540
  • <a962bc8508592c4d51092edac68579bd8b18fe44