mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: date <nobu@7501.net>
To: linux-kernel@vger.kernel.org
Subject: Fragmentation DoS?
Date: Sun, 20 Oct 2002 04:18:12 +0900 (JST)	[thread overview]
Message-ID: <200210191918.g9JJICT3032735@sh.7501.net> (raw)

To whom this may concern:

 It seems that when I run fragrouter-1.7 with a combination of
 -F3, -F4, -F5, and -T7 options, my linux kernel 2.4.18 will
 crash. I've tested this with fragrouter's 1.6 and 1.5, but have
 not yet been able to crash my kernel. To crash my 2.4.18 remotely
 with fragrouter 1.7 it usually takes about 15-20 tries. Maybe there
 is some sort of race condition occuring? I have also tried to
 crash my linux 2.2.x series kernals but have failed.

 Here are the sources I have been testing with:
 www.anzen.com/archive/research/fragrouter-1.7.tar.gz
 www.anzen.com/archive/research/fragrouter-1.6.tar.gz

 Here is the kernel oops message that I grabbed from messages:

general protection fault: 0000
CPU:    0
EIP:    0010:[<c0141099>]    Not tainted
EFLAGS: 00010246
eax: 00000000   ebx: ffffffff   ecx: 00000018   edx: c0141080
esi: c12c3e30   edi: ffffffff   ebp: ffffffff   esp: cfc95db0
ds: 0018   es: 0018   ss: 0018
Process sshd (pid: 59, stackpage=cfc95000)
Stack: 00000000 c0feb020 c01284ca ffffffff c12c3e30 00000001 00000001
000000f0
       c0feb000 c139c1a0 00000080 00000000 00000008 c12c3e30 00000246
c12c3e38
       000000f0 c01285f9 c12c3e30 000000f0 c0178612 00000000 00000000
00000008
Call Trace:    [<c01284ca>] [<c01285f9>] [<c0178612>] [<c0131a84>]
[<c0131b46>]
  [<c0131d88>] [<c0132428>] [<c01231fd>] [<c0123298>] [<c0151aa0>]
[<c01238a5>]
  [<c0123c03>] [<c012403c>] [<c0123f40>] [<c012fd56>] [<c012fca9>]
[<c01087eb>]

Code: f3 ab c7 43 48 00 00 00 00 8d 53 48 8d 43 4c 89 42 04 89 42

 Thanks for your time

 - nobu

             reply	other threads:[~2002-10-19 19:12 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-19 19:18 date [this message]
2002-10-19 21:07 ` Matti Aarnio
2002-10-25 15:42 ` Juri Haberland
2002-10-25 16:37   ` Mike Dresser
2002-10-25 16:44     ` Juri Haberland
2002-10-25 16:47       ` Mike Dresser

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=200210191918.g9JJICT3032735@sh.7501.net \
    --to=nobu@7501.net \
    --cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®