From: Chris Wright <chrisw@osdl.org>
To: linux-kernel@vger.kernel.org
Cc: greg@kroah.com, torvalds@osdl.org, akpm@osdl.org
Subject: Linux 2.6.11.6
Date: Fri, 25 Mar 2005 19:39:39 -0800 [thread overview]
Message-ID: <20050326033939.GV30522@shell0.pdx.osdl.net> (raw)
With some pending security fixes it's time to for a -stable update. So,
here's 2.6.11.6, in the normal kernel.org places. This includes some
security fixes, esp. one which closes a local root exploit in bluetooth.
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.5 and 2.6.11.6, as it is small enough to do so.
thanks,
-chris
--
Makefile | 2 +-
fs/binfmt_elf.c | 30 +++++++++++++++++-------------
fs/ext2/dir.c | 1 +
fs/isofs/inode.c | 5 +++++
fs/isofs/rock.c | 25 ++++++++++++++++++-------
net/bluetooth/af_bluetooth.c | 6 +++---
6 files changed, 45 insertions(+), 24 deletions(-)
Summary of changes from v2.6.11.5 to v2.6.11.6
==============================================
Chris Wright:
o isofs: more defensive checks against corrupt isofs images
o Linux 2.6.11.6
Herbert Xu:
o Potential DOS in load_elf_library
Linus Torvalds:
o isofs: Handle corupted rock-ridge info slightly better
o isofs: more "corrupted iso image" error cases
Marcel Holtmann:
o Fix signedness problem at socket creation
Mathieu Lafon:
o Suspected information leak (mem pages) in ext2
next reply other threads:[~2005-03-26 3:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20050326024616.GM28536@shell0.pdx.osdl.net>
2005-03-26 3:39 ` Chris Wright [this message]
2005-03-26 3:41 ` Linux 2.6.11.6 Chris Wright
2005-03-26 3:47 ` Hua Zhong
2005-03-26 3:56 ` Kyle Moffett
2005-03-26 3:58 ` Chris Wright
2005-03-26 8:50 ` Moritz Muehlenhoff
2005-03-26 9:27 ` Chris Wright
2005-03-27 18:52 ` Ryan Anderson
2005-03-27 18:59 ` Dave Jones
2005-03-27 19:59 ` 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=20050326033939.GV30522@shell0.pdx.osdl.net \
--to=chrisw@osdl.org \
--cc=akpm@osdl.org \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.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 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.