diff options
author | Jesper Juhl <jj@chaosbits.net> | 2011-07-29 18:38:49 +0400 |
---|---|---|
committer | Patrick McHardy <kaber@trash.net> | 2011-07-29 18:38:49 +0400 |
commit | 91c66c6893a3e2bb8a88a30cb76007d5d49d32c9 (patch) | |
tree | 1f37d40b668d46f305dd9088737c72ece4a91533 /net/bridge | |
parent | 00fe1ae91e0d69e52e8212d23cd3ecc74a7259a0 (diff) | |
download | linux-91c66c6893a3e2bb8a88a30cb76007d5d49d32c9.tar.xz |
netfilter: ip_queue: Fix small leak in ipq_build_packet_message()
ipq_build_packet_message() in net/ipv4/netfilter/ip_queue.c and
net/ipv6/netfilter/ip6_queue.c contain a small potential mem leak as
far as I can tell.
We allocate memory for 'skb' with alloc_skb() annd then call
nlh = NLMSG_PUT(skb, 0, 0, IPQM_PACKET, size - sizeof(*nlh));
NLMSG_PUT is a macro
NLMSG_PUT(skb, pid, seq, type, len) \
NLMSG_NEW(skb, pid, seq, type, len, 0)
that expands to NLMSG_NEW, which is also a macro which expands to:
NLMSG_NEW(skb, pid, seq, type, len, flags) \
({ if (unlikely(skb_tailroom(skb) < (int)NLMSG_SPACE(len))) \
goto nlmsg_failure; \
__nlmsg_put(skb, pid, seq, type, len, flags); })
If we take the true branch of the 'if' statement and 'goto
nlmsg_failure', then we'll, at that point, return from
ipq_build_packet_message() without having assigned 'skb' to anything
and we'll leak the memory we allocated for it when it goes out of
scope.
Fix this by placing a 'kfree(skb)' at 'nlmsg_failure'.
I admit that I do not know how likely this to actually happen or even
if there's something that guarantees that it will never happen - I'm
not that familiar with this code, but if that is so, I've not been
able to spot it.
Signed-off-by: Jesper Juhl <jj@chaosbits.net>
Signed-off-by: Patrick McHardy <kaber@trash.net>
Diffstat (limited to 'net/bridge')
0 files changed, 0 insertions, 0 deletions