From: Marcel Holtmann <marcel@holtmann.org>
To: Gabor MICSKO <gmicsko@szintezis.hu>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Fix prctl privilege escalation (CVE-2006-2451)
Date: Wed, 12 Jul 2006 18:05:53 +0200 [thread overview]
Message-ID: <1152720353.14173.16.camel@localhost> (raw)
In-Reply-To: <1152720258.4457.7.camel@localhost.localdomain>
Hi Gabor,
> Already fixed since 07/06/2006:
>
> http://www.kernel.org/git/?p=linux/kernel/git/stable/linux-2.6.17.y.git;a=commit;h=0af184bb9f80edfbb94de46cb52e9592e5a547b0
> http://www.kernel.org/git/?p=linux/kernel/git/stable/linux-2.6.17.y.git;a=commitdiff;h=0af184bb9f80edfbb94de46cb52e9592e5a547b0;hp=52cbb7b78994ea3799f1bbb8c03bce1e2f72a271
it is fixed in the stable tree, but it is not fixed upstream. It happens
that security fixes go into the stable tree, before the enter upstream.
Regards
Marcel
prev parent reply other threads:[~2006-07-12 16:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-12 11:12 Fix prctl privilege escalation (CVE-2006-2451) Marcel Holtmann
2006-07-12 16:04 ` Gabor MICSKO
2006-07-12 16:05 ` Marcel Holtmann [this message]
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=1152720353.14173.16.camel@localhost \
--to=marcel@holtmann.org \
--cc=gmicsko@szintezis.hu \
--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