diff options
| author | Marcelo Leitner <mleitner@redhat.com> | 2015-02-23 11:17:13 -0300 |
|---|---|---|
| committer | Jiri Slaby <jslaby@suse.cz> | 2015-11-18 12:45:11 +0100 |
| commit | 49f9add06964fe16997aa34099e7bb31c39b0314 (patch) | |
| tree | 81ea8a7a2107770c163a74549714c0dbc9b00c3e /arch/x86/include/asm/pgtable_64.h | |
| parent | 2b27106cd93020563185ea94618ea5019308226b (diff) | |
ipv6: addrconf: validate new MTU before applying it
commit 77751427a1ff25b27d47a4c36b12c3c8667855ac upstream.
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>
Signed-off-by: Jiri Slaby <jslaby@suse.cz>
Diffstat (limited to 'arch/x86/include/asm/pgtable_64.h')
0 files changed, 0 insertions, 0 deletions