From: sat <satadru@umich.edu>
To: linuxppc-dev@lists.linuxppc.org
Subject: GeeK: more proof...
Date: Thu, 08 Jun 2000 18:55:27 -0400 [thread overview]
Message-ID: <2712820046.960490527@[192.168.0.69]> (raw)
Can I apply the standard patch from 2.2.15 to 2.2.16 in Paul's CVS kernel?
---------- Forwarded Message ----------
Date: Thursday, June 08, 2000 1:23 AM -0400
From: Dug Song <dugsong@monkey.org>
To: backrow@citi.umich.edu
Subject: GeeK: more proof...
this is amazingly bad.
http://sendmail.net/?feed=000607linuxbug
A serious bug has been discovered in the Linux kernel that can be used
by local users to gain root access. The problem, a vulnerability in
the Linux kernel capability model, exists in kernel versions up to and
including version 2.2.15. According to Alan Cox, a key member of the
Linux developer community, "It will affect programs that drop setuid
state and rely on losing saved setuid, even those that check that the
setuid call succeeded."
-d.
---
http://www.monkey.org/~dugsong/
---------- End Forwarded Message ----------
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
reply other threads:[~2000-06-08 22:55 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='2712820046.960490527@[192.168.0.69]' \
--to=satadru@umich.edu \
--cc=linuxppc-dev@lists.linuxppc.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