Nixpkgs security tracker

Login with GitHub

Suggestion detail

Dismissed
(max. allowed matches exceeded)
created 23 hours ago Activity log
  • Created & dismissed (max. allowed matches exceeded) suggestion
net: ipv4: bound TCP reordering sysctl writes and MTU probe sizes

In the Linux kernel, the following vulnerability has been resolved: net: ipv4: bound TCP reordering sysctl writes and MTU probe sizes Reject invalid `net.ipv4.tcp_reordering` values before they reach TCP socket state. The sysctl is stored as an `int` but copied into the `u32` `tp->reordering` field for new sockets, so negative writes wrap to large values. With `tcp_mtu_probing=2`, the wrapped value can overflow the `tcp_mtu_probe()` size calculation and drive the MTU probing path into an out-of-bounds read. Route `tcp_reordering` writes through `proc_dointvec_minmax()` and require it to be at least 1. Also require `tcp_max_reordering` to be at least 1 so the configured maximum cannot become negative either. When registering the table for a non-init network namespace, relocate `extra2` pointers that refer into `init_net.ipv4` so the `tcp_reordering` upper bound follows that namespace's `tcp_max_reordering`. Harden `tcp_mtu_probe()` itself by computing `size_needed` as `u64`. This keeps the send queue and window checks from being bypassed through signed integer overflow.

Affected products

Linux
  • <bbae351c0f32f7c200249e4aa6561b2b419dcf69
  • <782708ca1ea1f68b8cbb5ea3a7f5f18d0000efae
  • =<6.18.*
  • <e81f805824a8109504fce090641b17d135b48cd1
  • <99206ce2244f8a3ed64298d0667c9055845a5dc7
  • =<6.12.*
  • <a094ac95d3b69adfa1676eb9c8eae6835d4f1671
  • <27ddf4486c7dbf5bdd393fa8bef6b67179796d98
  • <efb8763d7bbb40cff4cc55a6b62c3095a038149c
  • =<7.1.*
  • =<6.1.*
  • =<*
  • =<6.6.*
  • ==2.6.24
  • =<5.15.*
  • <f0d88a4cd03affff6c08adf6c63964e235aede43
  • <2.6.24
  • =<5.10.*