From: Greg KH <gregkh@suse.de>
To: linux-kernel@vger.kernel.org, torvalds@osdl.org, akpm@osdl.org,
stable@kernel.org
Subject: Linux 2.6.11.9
Date: Wed, 11 May 2005 15:54:49 -0700 [thread overview]
Message-ID: <20050511225448.GA12357@kroah.com> (raw)
Due to a recently announced security issue with the current kernel, we
(the -stable team) are announcing the release of the 2.6.11.9 kernel.
It contains:
- a fix for the posted problem
- a revert of a patch in the last release that caused issues
with partitions (the bk changelog shows this as a i2c issue,
but that is a mistake as you can see from the real patch.)
- addition of the SecurityBugs documentation
- another security related fix that is already in 2.6.12-rc4.
The diffstat and short summary of the fixes are below.
I'll also be replying to this message with a copy of the patch between
2.6.11.8 and 2.6.11.9, as it is small enough to do so.
thanks,
greg k-h
----------
Documentation/SecurityBugs | 38 ++++++++++++++++++++++++++++++++++++++
MAINTAINERS | 5 +++++
Makefile | 2 +-
REPORTING-BUGS | 4 ++++
fs/binfmt_elf.c | 4 ++--
fs/partitions/msdos.c | 5 -----
kernel/exit.c | 2 --
7 files changed, 50 insertions(+), 10 deletions(-)
Summary of changes from v2.6.11.8 to v2.6.11.9
==============================================
Andrew Morton:
o Remove bogus BUG() in kernel/exit.c
Chris Wright:
o Security contact info
Greg Kroah-Hartman:
o Cset exclude:
khali@linux-fr.org[gregkh]|ChangeSet|20050430010004|65088
o fix Linux kernel ELF core dump privilege elevation
o Linux 2.6.11.9
Jean Delvare:
o I2C: Fix incorrect sysfs file permissions in it87 and via686a
drivers
next reply other threads:[~2005-05-11 22:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-11 22:54 Greg KH [this message]
2005-05-11 22:55 ` Linux 2.6.11.9 Greg KH
2005-05-12 6:19 ` Michal Schmidt
2005-05-12 6:32 ` [stable] " 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=20050511225448.GA12357@kroah.com \
--to=gregkh@suse.de \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@kernel.org \
--cc=torvalds@osdl.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