Linux 2.6.11.9
Subsystems (4)
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:
[email protected][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
Documentation/SecurityBugs new file +38 -0
@@ -0,0 +1,38 @@ +Linux kernel developers take security very seriously. As such, we'd +like to know when a security bug is found so that it can be fixed and +disclosed as quickly as possible. Please report security bugs to the +Linux kernel security team. + +1) Contact + +The Linux kernel security team can be contacted by email at +<[email protected]>. This is a private list of security officers +who will help verify the bug report and develop and release a fix. +It is possible that the security team will bring in extra help from +area maintainers to understand and fix the security vulnerability. + +As it is with any bug, the more information provided the easier it +will be to diagnose and fix. Please review the procedure outlined in +REPORTING-BUGS if you are unclear about what information is helpful. +Any exploit code is very helpful and will not be released without +consent from the reporter unless it has already been made public. + +2) Disclosure + +The goal of the Linux kernel security team is to work with the +bug submitter to bug resolution as well as disclosure. We prefer +to fully disclose the bug as soon as possible. It is reasonable to +delay disclosure when the bug or the fix is not yet fully understood, +the solution is not well-tested or for vendor coordination. However, we +expect these delays to be short, measurable in days, not weeks or months. +A disclosure date is negotiated by the security team working with the +bug submitter as well as vendors. However, the kernel security team +holds the final say when setting a disclosure date. The timeframe for +disclosure is from immediate (esp. if it's already publically known) +to a few weeks. As a basic default policy, we expect report date to +disclosure date to be on the order of 7 days. + +3) Non-disclosure agreements + +The Linux kernel security team is not a formal body and therefore unable +to enter any non-disclosure agreements.
MAINTAINERS +5 -0
@@ -1966,6 +1966,11 @@ W: http://www.weinigel.se S: Supported +SECURITY CONTACT +P: Security Officers +M: [email protected] +S: Supported + SELINUX SECURITY MODULE P: Stephen Smalley M: [email protected]
Makefile +1 -1
@@ -1,7 +1,7 @@ VERSION = 2 PATCHLEVEL = 6 SUBLEVEL = 11 -EXTRAVERSION = .8 +EXTRAVERSION = .9 NAME=Woozy Beaver # *DOCUMENTATION*
REPORTING-BUGS +4 -0
@@ -16,6 +16,10 @@ describe how to recreate it. That is worth even more than the oops itself. The list of maintainers is in the MAINTAINERS file in this directory. + If it is a security bug, please copy the Security Contact listed +in the MAINTAINERS file. They can help coordinate bugfix and disclosure. +See Documentation/SecurityBugs for more infomation. + If you are totally stumped as to whom to send the report, send it to [email protected]. (For more information on the linux-kernel mailing list see http://www.tux.org/lkml/).
fs/binfmt_elf.c +2 -2
@@ -257,7 +257,7 @@ }/* Populate argv and envp */ - p = current->mm->arg_start; + p = current->mm->arg_end = current->mm->arg_start;while (argc-- >0 ) {size_t len;__put_user ((elf_addr_t )p, argv++);
@@ -1279,7 +1279,7 @@static int fill_psinfo (struct elf_prpsinfo *psinfo,struct task_struct *p,struct mm_struct *mm) { -int i, len; +unsigned int i, len;/* first copy the parameters from user space */ memset (psinfo,0 ,sizeof (struct elf_prpsinfo ));
fs/partitions/msdos.c +0 -5
@@ -114,9 +114,6 @@*/ for (i=0 ; i<4 ; i++, p++) {u32 offs, size, next; - -if (SYS_IND (p) ==0 ) -continue ;if (!NR_SECTS (p) ||is_extended_partition (p))continue ;
@@ -433,8 +430,6 @@for (slot =1 ; slot <=4 ; slot++, p++) {u32 start =START_SECT (p)*sector_size;u32 size =NR_SECTS (p)*sector_size; -if (SYS_IND (p) ==0 ) -continue ;if (!size)continue ;if (is_extended_partition (p)) {
kernel/exit.c +0 -2
@@ -516,8 +516,6 @@*/ BUG_ON (p == reaper || reaper->exit_state >=EXIT_ZOMBIE ); p->real_parent = reaper; -if (p->parent == p->real_parent) -BUG (); }static inline void reparent_thread (task_t *p,task_t *father,int traced)
Quoted 6 lines · Greg KH
Summary of changes from v2.6.11.8 to v2.6.11.9
==============================================
[...]
Jean Delvare:
o I2C: Fix incorrect sysfs file permissions in it87 and via686a drivers
This was already in 2.6.11.8, wasn't it?
Michal
Quoted 9 lines · * Michal Schmidt ([email protected]) wrote:
Quoted 6 lines · Greg KH
Summary of changes from v2.6.11.8 to v2.6.11.9
==============================================
[...]
Jean Delvare:
o I2C: Fix incorrect sysfs file permissions in it87 and via686a driversThis was already in 2.6.11.8, wasn't it?
Yes. There was a mixup, and the msdos partitions patch got mixed with this one (in 2.6.11.8). So that whole cset was backed out, and this fix was reapplied in 2.6.11.9.
thanks,
-chris