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 ago Activity log
  • Created & dismissed (max. allowed matches exceeded) suggestion
net: mvpp2: limit XDP frame size to the RX buffer

In the Linux kernel, the following vulnerability has been resolved: net: mvpp2: limit XDP frame size to the RX buffer mvpp2 has short and long BM pools, and short pool buffers can be smaller than PAGE_SIZE. The XDP path nevertheless initializes every xdp_buff with PAGE_SIZE as frame size. XDP helpers use frame_sz to validate tail growth and to derive the hard end of the data area. Advertising PAGE_SIZE for short buffers can let bpf_xdp_adjust_tail() grow a packet past the real allocation, corrupting memory or later tripping skb tailroom checks. Initialize the XDP buffer with bm_pool->frag_size so XDP tailroom matches the actual buffer backing the packet.

Affected products

Linux
  • <910617a4e67dbdd5fdb39d9dc6a51e491e1b2c3e
  • <f3c6aa078927e6fe8121c9c591ddee8716c5305a
  • =<6.18.*
  • =<6.1.*
  • <a3ee9231ccec6ec3be2de89c56f897055fd9eab1
  • ==5.9
  • =<6.6.*
  • =<5.15.*
  • =<6.12.*
  • =<7.0.*
  • <ec8e1e5842bc0dbd4c272761f4db3651eecd0339
  • <3b8b0c3631b19faee53f0d15a49924129b063eec
  • <994bd2b58d2bd08aa97ec0836cc813cfcb00d749
  • <9545cc5ef18ca22d031f2f47c157192460652359
  • <5.9
  • =<*