Searched hist:"77751427 a1ff25b27d47a4c36b12c3c8667855ac" (Results 1 – 1 of 1) sorted by relevance
| /openbmc/linux/net/ipv6/ |
| H A D | addrconf.c | diff 77751427a1ff25b27d47a4c36b12c3c8667855ac Mon Feb 23 08:17:13 CST 2015 Marcelo Leitner <mleitner@redhat.com> ipv6: addrconf: validate new MTU before applying it
Currently we don't check if the new MTU is valid or not and this allows
one to configure a smaller than minimum allowed by RFCs or even bigger
than interface own MTU, which is a problem as it may lead to packet
drops.
If you have a daemon like NetworkManager running, this may be exploited
by remote attackers by forging RA packets with an invalid MTU, possibly
leading to a DoS. (NetworkManager currently only validates for values
too small, but not for too big ones.)
The fix is just to make sure the new value is valid. That is, between
IPV6_MIN_MTU and interface's MTU.
Note that similar check is already performed at
ndisc_router_discovery(), for when kernel itself parses the RA.
Signed-off-by: Marcelo Ricardo Leitner <mleitner@redhat.com>
Signed-off-by: Sabrina Dubroca <sd@queasysnail.net>
Signed-off-by: David S. Miller <davem@davemloft.net>
|