From: Greg KH <greg@kroah.com>
To: Oliver Pinter <oliver.pntr@gmail.com>
Cc: Bastian Blank <bastian@waldi.eu.org>,
Niki Denev <ndenev@gmail.com>, Willy Tarreau <w@1wt.eu>,
linux-kernel@vger.kernel.org, jens.axboe@oracle.com,
stable@kernel.org
Subject: Re: [stable] [PATCH] kernel 2.6.24.1 still vulnerable to the vmsplice local root exploit
Date: Sun, 10 Feb 2008 09:05:44 -0800 [thread overview]
Message-ID: <20080210170544.GA25353@kroah.com> (raw)
In-Reply-To: <6101e8c40802100502g6c3c2d01ufce1ce23c7c20c5a@mail.gmail.com>
On Sun, Feb 10, 2008 at 02:02:27PM +0100, Oliver Pinter wrote:
> thx it fixed for 2.6.22
>
> >>>>>>>
>
> commit f6e993b835393543bab2d917f9dea75218473edd
> Author: Oliver Pinter <oliver.pntr@gmail.com>
> Date: Sun Feb 10 14:03:46 2008 +0100
>
> [PATCH] vm: splice local root exploit fix for 2.6.22.y
>
> Based on Bastian Blank's patch
>
> Fix for CVE_2008_0009 and CVE_2008-0010
>
> ----->8-----
>
> oliver@pancs:/tmp$ ./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: 0xb7f1a000 .. 0xb7f4c000
> [-] vmsplice: Bad address
>
> -----8<-----
>
> Signed-off-by: Oliver Pinter <oliver.pntr@gmail.com>
>
> diff --git a/fs/splice.c b/fs/splice.c
> index e263d3b..d8b106e 100644
> --- a/fs/splice.c
> +++ b/fs/splice.c
> @@ -1182,6 +1182,12 @@ static int get_iovec_page_array(const struct
> iovec __user *iov,
> if (unlikely(!base))
> break;
>
> + /* CVE-2008-0009, CVE-2008-0010 fix */
No, this is a different CVE, as it is a different problem from the
original 09 and 10 report.
It has been given CVE-2008-0600 to address this issue (09 and 10 only
affect .23 and .24 kernels, and have been fixed.)
> + if(!access_ok(VERIFY_READ, base, len)) {
> + error = -EFAULT;
> + break;
> + }
Hm, perhaps we should just properly check the len field instead? That's
what is being overflowed here...
thanks,
greg k-h
next prev parent reply other threads:[~2008-02-10 17:07 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
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 ` Greg KH [this message]
2008-02-10 17:11 ` [stable] " 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=20080210170544.GA25353@kroah.com \
--to=greg@kroah.com \
--cc=bastian@waldi.eu.org \
--cc=jens.axboe@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ndenev@gmail.com \
--cc=oliver.pntr@gmail.com \
--cc=stable@kernel.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®