From: "Oliver Pinter" <oliver.pntr@gmail.com>
To: "Niki Denev" <ndenev@gmail.com>
Cc: "Willy Tarreau" <w@1wt.eu>,
linux-kernel@vger.kernel.org, jens.axboe@oracle.com,
"Andrew Morton" <akpm@linux-foundation.org>,
"Greg KH" <gregkh@suse.de>, "Greg KH" <greg@kroah.com>,
"Linus Torvalds" <torvalds@linux-foundation.org>,
stable@kernel.org
Subject: Re: [PATCH] kernel 2.6.24.1 still vulnerable to the vmsplice local root exploit
Date: Sun, 10 Feb 2008 13:04:38 +0100 [thread overview]
Message-ID: <6101e8c40802100404s28ae49f3q5923867ce3257713@mail.gmail.com> (raw)
In-Reply-To: <2e77fc10802100140q5c8adfb4k7db88d48cbd5f8b2@mail.gmail.com>
hmmm, with 2.6.22.y serie is too affected
Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
Last login: Sat Feb 9 15:34:35 2008
oliver@home:~$ ./2617_26241_root_exploit
-----------------------------------
Linux vmsplice Local Root Exploit
By qaaz
-----------------------------------
[+] mmap: 0x0 .. 0x1000
[+] page: 0x0
[+] page: 0x20
[+] mmap: 0x4000 .. 0x5000
[+] page: 0x4000
[+] page: 0x4020
[+] mmap: 0x1000 .. 0x2000
[+] page: 0x1000
[+] mmap: 0xb7f79000 .. 0xb7fab000
[+] root
root@home:~# uname -a
Linux home 2.6.22.17 #3 SMP PREEMPT Mon Feb 4 17:38:33 CET 2008 i686 GNU/Linux
root@home:~#
--
Thanks,
Oliver
next prev parent reply other threads:[~2008-02-10 12:04 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-10 6:04 Niki Denev
2008-02-10 6:32 ` Willy Tarreau
2008-02-10 6:38 ` Niki Denev
2008-02-10 9:40 ` [PATCH] " Niki Denev
2008-02-10 12:04 ` Oliver Pinter [this message]
2008-02-10 12:22 ` Bastian Blank
2008-02-10 12:39 ` Niki Denev
2008-02-10 12:47 ` Bastian Blank
2008-02-10 12:54 ` Niki Denev
2008-02-10 13:02 ` Oliver Pinter
2008-02-10 17:05 ` [stable] " Greg KH
2008-02-10 17:11 ` Pekka Enberg
2008-02-10 17:44 ` Oliver Pinter
2008-02-10 17:48 ` Oliver Pinter
2008-02-10 13:48 ` Niki Denev
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=6101e8c40802100404s28ae49f3q5923867ce3257713@mail.gmail.com \
--to=oliver.pntr@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=greg@kroah.com \
--cc=gregkh@suse.de \
--cc=jens.axboe@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ndenev@gmail.com \
--cc=stable@kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=w@1wt.eu \
/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®