From: Greg KH <gregkh@suse.de>
To: unlisted-recipients:; (no To-header on input)
Cc: security@isec.pl, linux-kernel@vger.kernel.org,
full-disclosure@lists.netsys.com, bugtraq@securityfocus.com,
vulnwatch@vulnwatch.org
Subject: Re: Linux kernel ELF core dump privilege elevation
Date: Wed, 11 May 2005 11:30:46 -0700 [thread overview]
Message-ID: <20050511183046.GA17112@kroah.com> (raw)
In-Reply-To: <20050511181211.GA16652@kroah.com>
On Wed, May 11, 2005 at 11:12:11AM -0700, Greg KH wrote:
> On Wed, May 11, 2005 at 01:08:56PM +0200, Paul Starzetz wrote:
> > Hi,
> >
> > since it became clear from the discussion in January about the uselib()
> > vulnerability, that the Linux community prefers full, non-embargoed
> > disclosure of kernel bugs, I release full details right now. However to
> > follows at least some of the responsable disclosure rules, no exploit code will be
> > released. Instead, only a proof-of-concept code is released to demonstrate
> > the vulnerability.
>
> <snip>
>
> And here's a patch for 2.6 that is completly untested. I'll work on
> testing it today and if it works, we will release a new 2.6.11.y release
> with this fix in it.
>
> thanks,
>
> greg k-h
>
>
> Subject: possibly fix Linux kernel ELF core dump privilege elevation
>
> As noted by Paul Starzetz
>
> references CAN-something-I-need-to-go-look-up...
CAN-2005-1263 is the correct one. Sorry for being lazy and not looking
it up right away.
thanks,
greg k-h
next prev parent reply other threads:[~2005-05-11 18:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.44.0505101615410.1618-100000@isec.pl>
2005-05-11 18:12 ` Linux kernel ELF core dump privilege elevation Greg KH
2005-05-11 18:30 ` Greg KH [this message]
2005-05-11 21:51 ` Paul Starzetz
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=20050511183046.GA17112@kroah.com \
--to=gregkh@suse.de \
--cc=bugtraq@securityfocus.com \
--cc=full-disclosure@lists.netsys.com \
--cc=linux-kernel@vger.kernel.org \
--cc=security@isec.pl \
--cc=vulnwatch@vulnwatch.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 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.