From: Lee Revell <rlrevell@joe-job.com>
To: bert hubert <ahu@ds9a.nl>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: local root exploit confirmed in 2.6.10: Linux 2.6 Kernel Capability LSM Module Local Privilege Elevation
Date: Wed, 29 Dec 2004 05:32:59 -0500 [thread overview]
Message-ID: <1104316379.2984.26.camel@krustophenia.net> (raw)
In-Reply-To: <20041229102532.GB9926@outpost.ds9a.nl>
On Wed, 2004-12-29 at 11:25 +0100, bert hubert wrote:
> On Tue, Dec 28, 2004 at 04:21:55PM -0500, Lee Revell wrote:
> > Frank Barknecht pointed this out on linux-audio-dev, it's a horrible
> > bug, I confirmed it in 2.6.10, and have not seen it mentioned on the
> > list.
>
> Although this sucks, it should be pointed out that it only grants root to
> users able to force the loading of a certain module, aka 'root'.
Not force the loading of a certain module, but predict when it will be
loaded. Still, not easy to exploit.
Lee
next prev parent reply other threads:[~2004-12-29 10:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-28 21:21 local root exploit confirmed in 2.6.10: Linux 2.6 Kernel Capability LSM Module Local Privilege Elevation Lee Revell
2004-12-28 21:53 ` Lee Revell
2004-12-29 10:25 ` bert hubert
2004-12-29 10:32 ` Lee Revell [this message]
2004-12-29 14:01 ` Serge E. Hallyn
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=1104316379.2984.26.camel@krustophenia.net \
--to=rlrevell@joe-job.com \
--cc=ahu@ds9a.nl \
--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 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.