mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Chris Wright <chrisw@osdl.org>
To: Chris White <webmaster@securesystem.info>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Kernel fchown() exploit status?
Date: Thu, 8 Jul 2004 16:24:14 -0700	[thread overview]
Message-ID: <20040708162414.I1973@build.pdx.osdl.net> (raw)
In-Reply-To: <40EDB764.6060107@securesystem.info>; from webmaster@securesystem.info on Fri, Jul 09, 2004 at 06:06:44AM +0900

* Chris White (webmaster@securesystem.info) wrote:
> There was a recent security announcment regarding a vulnerability with 
> the fchown function.
> 
> Only a few distrobutions (red hat/suse) have fixed the issue, but I've 
> yet to see a general patch for it.

Patches are in both 2.4 and 2.6 bk trees.  2.4.27-rc3 has this fixed.
There hasn't been a 2.6.8-rc release since the patches went in to 2.6

For 2.4 see these patches:
http://linux.bkbits.net:8080/linux-2.4/cset@40e725f8sMbNK6BEQmRi5fWfux8l8A
http://linux.bkbits.net:8080/linux-2.4/cset@40e733598ODR85iS5HRft0zJTnDCHA

For 2.6 see these patches:
http://linux.bkbits.net:8080/linux-2.6/cset@40e62e18vom8K1fHgbJfe1oQ6mdkkQ
http://linux.bkbits.net:8080/linux-2.6/cset@40e6158bme9avS6IqahBN0wa9zx7LQ

thanks,
-chris
-- 
Linux Security Modules     http://lsm.immunix.org     http://lsm.bkbits.net

  parent reply	other threads:[~2004-07-08 23:24 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-08 21:06 Chris White
2004-07-08 21:54 ` Manuel Arostegui Ramirez
2004-07-08 23:24 ` Chris Wright [this message]
2004-07-09  9:46   ` Michael Buesch
2004-07-09 10:02     ` Manuel Arostegui Ramirez
2004-07-09 18:17     ` Chris Wright

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=20040708162414.I1973@build.pdx.osdl.net \
    --to=chrisw@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=webmaster@securesystem.info \
    /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®