We (the -stable team) are announcing the release of the 2.6.23.14
kernel.
It contains a single fix for a problem that could cause a local user to
cause file system corruption on some types of filesystems.
All users of the 2.6.23 series are encouraged to upgrade.
I'll also be replying to this message with a copy of the patch between
2.6.23.13 and 2.6.23.14
The updated 2.6.23.y git tree can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-2.6.23.y.git
and can be browsed at the normal kernel.org git web browser:
http://git.kernel.org/?p=linux/kernel/git/stable/linux-2.6.23.y.git;a=summary
thanks,
greg k-h
--------
Makefile | 2 +-
fs/namei.c | 4 ++--
2 files changed, 3 insertions(+), 3 deletions(-)
Summary of changes from v2.6.23.13 to v2.6.23.14
================================================
Greg Kroah-Hartman (1):
Linux 2.6.23.14
Linus Torvalds (1):
Use access mode instead of open flags to determine needed permissions (CVE-2008-0001)
diff --git a/Makefile b/Makefile
index 55edf2f..5c31700 100644
--- a/Makefile
+++ b/Makefile
@@ -1,7 +1,7 @@
VERSION = 2
PATCHLEVEL = 6
SUBLEVEL = 23
-EXTRAVERSION = .13
+EXTRAVERSION = .14
NAME = Arr Matey! A Hairy Bilge Rat!
# *DOCUMENTATION*
diff --git a/fs/namei.c b/fs/namei.c
index a83160a..314afe6 100644
--- a/fs/namei.c
+++ b/fs/namei.c
@@ -1576,7 +1576,7 @@ int may_open(struct nameidata *nd, int acc_mode, int flag)
if (S_ISLNK(inode->i_mode))
return -ELOOP;
- if (S_ISDIR(inode->i_mode) && (flag & FMODE_WRITE))
+ if (S_ISDIR(inode->i_mode) && (acc_mode & MAY_WRITE))
return -EISDIR;
error = vfs_permission(nd, acc_mode);
@@ -1595,7 +1595,7 @@ int may_open(struct nameidata *nd, int acc_mode, int flag)
return -EACCES;
flag &= ~O_TRUNC;
- } else if (IS_RDONLY(inode) && (flag & FMODE_WRITE))
+ } else if (IS_RDONLY(inode) && (acc_mode & MAY_WRITE))
return -EROFS;
/*
* An append-only file must be opened in append mode for writing.
* Greg Kroah-Hartman <[email protected]> wrote:
> It contains a single fix for a problem that could cause a local
> user to cause file system corruption on some types of filesystems.
Some types of filesystems? Which ones?
--
left blank, right bald
On Wed, Jan 16, 2008 at 03:27:41PM +0100, markus reichelt wrote:
> * Greg Kroah-Hartman <[email protected]> wrote:
>
> > It contains a single fix for a problem that could cause a local
> > user to cause file system corruption on some types of filesystems.
>
> Some types of filesystems? Which ones?
Lots of them, but not all :)