From: "David S. Miller" <davem@redhat.com>
To: James Morris <jmorris@redhat.com>
Cc: netfilter-devel@lists.netfilter.org, laforge@netfilter.org,
netdev@oss.sgi.com, arjanv@redhat.com, kuznet@ms2.inr.ac.ru
Subject: Re: Remote DoS vulnerability in Linux kernel 2.6.x (fwd)
Date: Wed, 30 Jun 2004 14:42:30 -0700 [thread overview]
Message-ID: <20040630144230.1d52864b.davem@redhat.com> (raw)
In-Reply-To: <Xine.LNX.4.44.0406301507320.32316-100000@thoron.boston.redhat.com>
On Wed, 30 Jun 2004 15:11:25 -0400 (EDT)
James Morris <jmorris@redhat.com> wrote:
> FYI, I have audited options parsing code in TCP, IPv4 input and Netfilter
> for any similar problems and not found any. Further review would be
> useful (I have not looked at the IPv6 header parsing for example).
I can't find any other cases.
This bug only came up because up the huge change Rusty and Harald did
to make these modules not access the SKB header data directly, and
instead to use local on-stack copies and skb_copy_bits().
next prev parent reply other threads:[~2004-06-30 21:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-30 18:24 Remote DoS vulnerability in Linux kernel 2.6.x (fwd) James Morris
2004-06-30 19:11 ` James Morris
2004-06-30 21:42 ` David S. Miller [this message]
2004-07-01 9:10 ` Harald Welte
2004-07-01 8:59 ` Jozsef Kadlecsik
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=20040630144230.1d52864b.davem@redhat.com \
--to=davem@redhat.com \
--cc=arjanv@redhat.com \
--cc=jmorris@redhat.com \
--cc=kuznet@ms2.inr.ac.ru \
--cc=laforge@netfilter.org \
--cc=netdev@oss.sgi.com \
--cc=netfilter-devel@lists.netfilter.org \
/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.