From: Mathias Krause <minipli@googlemail.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>,
linux-mm@kvack.org, security@kernel.org
Subject: Re: [Security] DoS on x86_64
Date: Thu, 28 Jan 2010 22:49:24 +0100 [thread overview]
Message-ID: <2BCD2997-7101-4BFF-82CC-A5EC2F4F8E9E@googlemail.com> (raw)
In-Reply-To: <alpine.LFD.2.00.1001280902340.22433@localhost.localdomain>
[-- Attachment #1: Type: text/plain, Size: 1538 bytes --]
Am 28.01.2010 um 18:10 schrieb Linus Torvalds:
>
>
> On Thu, 28 Jan 2010, Mathias Krause wrote:
>>
>> 1. Enable core dumps
>> 2. Start an 32 bit program that tries to execve() an 64 bit program
>> 3. The 64 bit program cannot be started by the kernel because it
>> can't find
>> the interpreter, i.e. execve returns with an error
>> 4. Generate a segmentation fault
>> 5. panic
>
> Hmm. Nothing happens for me when I try this. I just get the expected
> SIGSEGV. Can you post the oops/panic message?
>
I currently have no access to the actual machine but will send it to
you tomorrow.
> I don't get a core-dump, even though it says I do:
>
> [torvalds@nehalem amd64_killer]$ ./run.sh
> * look at /proc/22768/maps and press enter to continue...
> * executing ./poison...
> * that failed (No such file or directory), as expected :)
> * look at /proc/22768/maps and press enter to continue...
Have you looked at /proc/PID/maps at this point? On our machine the
[vdso] was gone and [vsyscall] was there instead -- at an 64 bit
address of course.
> * fasten your seat belt, generating segmentation fault...
> ./run.sh: line 6: 22768 Segmentation fault (core dumped) ./
> amd64_killer ./poison
>
> This is with current -git (I don't have any machines around running
> older
> kernels), so maybe we fixed it already, of course.
Since this is a production server I would rather stick to a stable
kernel and just pick the commit that fixes the issue. Can you please
tell me which one that may be?
Greets,
Mathias
[-- Attachment #2: Signierter Teil der Nachricht --]
[-- Type: application/pgp-signature, Size: 186 bytes --]
next prev parent reply other threads:[~2010-01-28 21:49 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-28 7:34 Mathias Krause
2010-01-28 8:18 ` [Security] " Andrew Morton
2010-01-28 15:41 ` H. Peter Anvin
2010-01-28 22:33 ` Linus Torvalds
2010-01-28 22:47 ` Mathias Krause
2010-01-28 22:47 ` H. Peter Anvin
2010-01-28 23:09 ` Linus Torvalds
2010-01-28 23:27 ` H. Peter Anvin
2010-01-28 23:46 ` Linus Torvalds
2010-01-29 4:43 ` Linus Torvalds
2010-01-29 4:43 ` [PATCH 1/2] Split 'flush_old_exec' into two functions Linus Torvalds
2010-01-29 4:47 ` [PATCH 2/2] x86: get rid of the insane TIF_ABI_PENDING bit Linus Torvalds
2010-01-29 5:17 ` [PATCH 1/2] Split 'flush_old_exec' into two functions H. Peter Anvin
2010-01-29 5:05 ` [Security] DoS on x86_64 H. Peter Anvin
2010-01-29 5:29 ` H. Peter Anvin
2010-01-29 5:34 ` [PATCH 1/2] Split 'flush_old_exec' into two functions H. Peter Anvin
2010-01-29 5:34 ` [PATCH 2/2] x86: get rid of the insane TIF_ABI_PENDING bit H. Peter Anvin
2010-01-29 5:36 ` [PATCH 1/2] Split 'flush_old_exec' into two functions H. Peter Anvin
2010-01-29 5:36 ` [PATCH 2/2] x86: get rid of the insane TIF_ABI_PENDING bit H. Peter Anvin
2010-01-29 5:41 ` [PATCH 1/2] Split 'flush_old_exec' into two functions H. Peter Anvin
2010-01-29 5:41 ` [PATCH 2/2] x86: get rid of the insane TIF_ABI_PENDING bit H. Peter Anvin
2010-01-29 5:44 ` H. Peter Anvin
2010-01-29 6:14 ` [PATCH 1/2] Split 'flush_old_exec' into two functions H. Peter Anvin
2010-01-29 6:14 ` [PATCH 2/2] x86: get rid of the insane TIF_ABI_PENDING bit H. Peter Anvin
2010-01-28 23:06 ` [Security] DoS on x86_64 Linus Torvalds
2010-01-28 23:14 ` H. Peter Anvin
2010-01-28 21:31 ` Mathias Krause
2010-01-28 17:10 ` Linus Torvalds
2010-01-28 21:49 ` Mathias Krause [this message]
2010-01-28 21:58 ` Linus Torvalds
2010-01-28 22:08 ` Mathias Krause
2010-01-28 22:18 ` Linus Torvalds
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=2BCD2997-7101-4BFF-82CC-A5EC2F4F8E9E@googlemail.com \
--to=minipli@googlemail.com \
--cc=linux-mm@kvack.org \
--cc=mingo@redhat.com \
--cc=security@kernel.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.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