{"push_id":907491263,"size":2,"distinct_size":2,"ref":"refs/heads/m","head":"fde57df2d4a2f5b76484ca95eb9592b3f9d9a5a9","before":"337125c05c29f73782f7dfb880c28e2086b70445","commits":[{"sha":"0358e12e499c1f80096f9a213a91ca28e87dd764","author":{"email":"518d07701a80fb29f0da45c7c615106b9be9d5c6@redhat.com","name":"Marcelo Leitner"},"message":"ipv6: addrconf: validate new MTU before applying it\n\nCurrently we don't check if the new MTU is valid or not and this allows\none to configure a smaller than minimum allowed by RFCs or even bigger\nthan interface own MTU, which is a problem as it may lead to packet\ndrops.\n\nIf you have a daemon like NetworkManager running, this may be exploited\nby remote attackers by forging RA packets with an invalid MTU, possibly\nleading to a DoS. (NetworkManager currently only validates for values\ntoo small, but not for too big ones.)\n\nThe fix is just to make sure the new value is valid. That is, between\nIPV6_MIN_MTU and interface's MTU.\n\nNote that similar check is already performed at\nndisc_router_discovery(), for when kernel itself parses the RA.\n\nChange-Id: I6b70d0c12a77c7932066982f8797d8024f130d7c\nSigned-off-by: Marcelo Ricardo Leitner <mleitner@redhat.com>\nSigned-off-by: Sabrina Dubroca <sd@queasysnail.net>\nSigned-off-by: David S. Miller <davem@davemloft.net>","distinct":true,"url":"https://api.github.com/repos/DirtyUnicorns/android_kernel_moto_shamu/commits/0358e12e499c1f80096f9a213a91ca28e87dd764"},{"sha":"fde57df2d4a2f5b76484ca95eb9592b3f9d9a5a9","author":{"email":"53a9640965581ea5da35b0a056cf1b024631e319@gmail.com","name":"Josh Chasky"},"message":"Merge \"ipv6: addrconf: validate new MTU before applying it\" into m","distinct":true,"url":"https://api.github.com/repos/DirtyUnicorns/android_kernel_moto_shamu/commits/fde57df2d4a2f5b76484ca95eb9592b3f9d9a5a9"}]}