From: Patrick McHardy <kaber@trash.net>
To: mukesh agrawal <mukesh@cs.cmu.edu>
Cc: coreteam@netfilter.org, netfilter-devel@lists.netfilter.org,
trivial@rustcorp.com.au, linux-kernel@vger.kernel.org
Subject: Re: [netfilter-core] [PATCH 2.6.10 1/1] netfilter: fix crash on nat+icmp packets
Date: Wed, 02 Mar 2005 10:26:41 +0100 [thread overview]
Message-ID: <422586D1.5000609@trash.net> (raw)
In-Reply-To: <Pine.LNX.4.61.0503011830590.31296@slash.mukesh.agrawals.org>
mukesh agrawal wrote:
> The cause of the crash is that udp_manip_pkt reads *pskb into iph before
> calling skb_ip_make_writable, and fails to update iph after the call.
> Since skb_ip_make_writable may delete the original skb when it makes a
> copy, a page fault may occur when udp_manip_pkt later dereferences iph.
This bug has already been fixed in 2.6.11-rc.
Regards
Patrick
>
> diff -uprN linux-2.6.10.orig/net/ipv4/netfilter/ip_nat_proto_udp.c
> linux-2.6.10.fixed/net/ipv4/netfilter/ip_nat_proto_udp.c
> --- linux-2.6.10.orig/net/ipv4/netfilter/ip_nat_proto_udp.c
> 2004-12-24 16:34:01.000000000 -0500
> +++ linux-2.6.10.fixed/net/ipv4/netfilter/ip_nat_proto_udp.c
> 2005-03-01 19:32:21.000000000 -0500
> @@ -95,6 +95,9 @@ udp_manip_pkt(struct sk_buff **pskb,
>
> if (!skb_ip_make_writable(pskb, hdroff + sizeof(hdr)))
> return 0;
> + /* skb_ip_make_writable may have copied the skb, and deleted
> + the original */
> + iph = (struct iphdr *)((*pskb)->data + iphdroff);
>
> hdr = (void *)(*pskb)->data + hdroff;
> if (maniptype == IP_NAT_MANIP_SRC) {
>
prev parent reply other threads:[~2005-03-02 9:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-02 1:41 [PATCH 2.6.10 1/1] netfilter: fix crash on nat+icmp packets mukesh agrawal
2005-03-02 9:26 ` Patrick McHardy [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=422586D1.5000609@trash.net \
--to=kaber@trash.net \
--cc=coreteam@netfilter.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mukesh@cs.cmu.edu \
--cc=netfilter-devel@lists.netfilter.org \
--cc=trivial@rustcorp.com.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.