igmp: limit igmpv3_newpack() packet size to IP_MAX_MTU
authorEric Dumazet <edumazet@google.com>
Tue, 5 Sep 2023 04:23:38 +0000 (04:23 +0000)
committerDavid S. Miller <davem@davemloft.net>
Tue, 5 Sep 2023 16:49:40 +0000 (17:49 +0100)
commitc3b704d4a4a265660e665df51b129e8425216ed1
treecf8d488ca7e6e0133504e5137a218d87436d5c22
parentd3287e4038ca4f81e02067ab72d087af7224c68b
igmp: limit igmpv3_newpack() packet size to IP_MAX_MTU

This is a follow up of commit 915d975b2ffa ("net: deal with integer
overflows in kmalloc_reserve()") based on David Laight feedback.

Back in 2010, I failed to realize malicious users could set dev->mtu
to arbitrary values. This mtu has been since limited to 0x7fffffff but
regardless of how big dev->mtu is, it makes no sense for igmpv3_newpack()
to allocate more than IP_MAX_MTU and risk various skb fields overflows.

Fixes: 57e1ab6eaddc ("igmp: refine skb allocations")
Link: https://lore.kernel.org/netdev/d273628df80f45428e739274ab9ecb72@AcuMS.aculab.com/
Signed-off-by: Eric Dumazet <edumazet@google.com>
Reported-by: David Laight <David.Laight@ACULAB.COM>
Cc: Kyle Zeng <zengyhkyle@gmail.com>
Reviewed-by: Simon Horman <horms@kernel.org>
Signed-off-by: David S. Miller <davem@davemloft.net>
net/ipv4/igmp.c