]> git.ipfire.org Git - thirdparty/kernel/stable-queue.git/commitdiff
2.6.16.6 release v2.6.16.6
authorGreg Kroah-Hartman <gregkh@suse.de>
Mon, 17 Apr 2006 21:12:50 +0000 (14:12 -0700)
committerGreg Kroah-Hartman <gregkh@suse.de>
Mon, 17 Apr 2006 21:12:50 +0000 (14:12 -0700)
25 files changed:
2.6.16.6/CIFS-Incorrect-signature-sent-on-SMB-Read.patch [moved from review-2.6.16/CIFS-Incorrect-signature-sent-on-SMB-Read.patch with 100% similarity]
2.6.16.6/Fix-suspend-with-traced-tasks.patch [moved from review-2.6.16/Fix-suspend-with-traced-tasks.patch with 100% similarity]
2.6.16.6/RLIMIT_CPU-fix-handling-of-a-zero-limit.patch [moved from review-2.6.16/RLIMIT_CPU-fix-handling-of-a-zero-limit.patch with 100% similarity]
2.6.16.6/XFS-Fix-utime-2-in-the-case-that-no-times-parameter-was-passed-in.patch [moved from review-2.6.16/XFS-Fix-utime-2-in-the-case-that-no-times-parameter-was-passed-in.patch with 100% similarity]
2.6.16.6/alpha-smp-boot-fixes.patch [moved from review-2.6.16/alpha-smp-boot-fixes.patch with 100% similarity]
2.6.16.6/atm-clip-causes-unregister-hang.patch [moved from review-2.6.16/atm-clip-causes-unregister-hang.patch with 100% similarity]
2.6.16.6/cciss-bug-fix-for-crash-when-running-hpacucli.patch [moved from review-2.6.16/cciss-bug-fix-for-crash-when-running-hpacucli.patch with 100% similarity]
2.6.16.6/edac_752x-needs-config_hotplug.patch [moved from review-2.6.16/edac_752x-needs-config_hotplug.patch with 100% similarity]
2.6.16.6/ext3-fix-missed-mutex-unlock.patch [moved from review-2.6.16/ext3-fix-missed-mutex-unlock.patch with 100% similarity]
2.6.16.6/fix-block-device-symlink-name.patch [moved from review-2.6.16/fix-block-device-symlink-name.patch with 100% similarity]
2.6.16.6/fix-buddy-list-race-that-could-lead-to-page-lru-list-corruptions.patch [moved from review-2.6.16/fix-buddy-list-race-that-could-lead-to-page-lru-list-corruptions.patch with 100% similarity]
2.6.16.6/fix-non-leader-exec-under-ptrace.patch [moved from review-2.6.16/fix-non-leader-exec-under-ptrace.patch with 100% similarity]
2.6.16.6/fuse-fix-oops-in-fuse_send_readpages.patch [moved from review-2.6.16/fuse-fix-oops-in-fuse_send_readpages.patch with 100% similarity]
2.6.16.6/isd200-limit-to-blk_dev_ide.patch [moved from review-2.6.16/isd200-limit-to-blk_dev_ide.patch with 100% similarity]
2.6.16.6/m32r-fix-cpu_possible_map-and-cpu_present_map-initialization-for-smp-kernel.patch [moved from review-2.6.16/m32r-fix-cpu_possible_map-and-cpu_present_map-initialization-for-smp-kernel.patch with 100% similarity]
2.6.16.6/m32r-security-fix-of-get-put-_user-macros.patch [moved from review-2.6.16/m32r-security-fix-of-get-put-_user-macros.patch with 100% similarity]
2.6.16.6/mpbl0010-driver-sysfs-permissions-wide-open.patch [moved from review-2.6.16/mpbl0010-driver-sysfs-permissions-wide-open.patch with 100% similarity]
2.6.16.6/netfilter-fix-fragmentation-issues-with-bridge-netfilter.patch [moved from review-2.6.16/netfilter-fix-fragmentation-issues-with-bridge-netfilter.patch with 100% similarity]
2.6.16.6/powerpc-fix-incorrect-sa_onstack-behaviour-for-64-bit-processes.patch [moved from review-2.6.16/powerpc-fix-incorrect-sa_onstack-behaviour-for-64-bit-processes.patch with 100% similarity]
2.6.16.6/powerpc-iseries-needs-slb_initialize-to-be-called.patch [moved from review-2.6.16/powerpc-iseries-needs-slb_initialize-to-be-called.patch with 100% similarity]
2.6.16.6/send.mbox [moved from review-2.6.16/send.mbox with 100% similarity]
2.6.16.6/series [moved from review-2.6.16/series with 93% similarity]
2.6.16.6/shmat-stop-mprotect-from-giving-write-permission-to-a-readonly-attachment.patch [new file with mode: 0644]
2.6.16.6/sky2-bad-memory-reference-on-dual-port-cards.patch [moved from review-2.6.16/sky2-bad-memory-reference-on-dual-port-cards.patch with 100% similarity]
2.6.16.6/usb-remove-__init-from-usb_console_setup.patch [moved from review-2.6.16/usb-remove-__init-from-usb_console_setup.patch with 100% similarity]

similarity index 100%
rename from review-2.6.16/send.mbox
rename to 2.6.16.6/send.mbox
similarity index 93%
rename from review-2.6.16/series
rename to 2.6.16.6/series
index 0561b4b206cf27dead8f4b6057ab48501a246c1f..1b6e9612b50fd4eac9de07123591215c52e69340 100644 (file)
@@ -20,3 +20,4 @@ Fix-suspend-with-traced-tasks.patch
 usb-remove-__init-from-usb_console_setup.patch
 fix-non-leader-exec-under-ptrace.patch
 atm-clip-causes-unregister-hang.patch
+shmat-stop-mprotect-from-giving-write-permission-to-a-readonly-attachment.patch
diff --git a/2.6.16.6/shmat-stop-mprotect-from-giving-write-permission-to-a-readonly-attachment.patch b/2.6.16.6/shmat-stop-mprotect-from-giving-write-permission-to-a-readonly-attachment.patch
new file mode 100644 (file)
index 0000000..7cfaf49
--- /dev/null
@@ -0,0 +1,60 @@
+From akpm@osdl.org Wed Apr 12 14:32:33 2006
+Message-Id: <200604122132.k3CLW1Io021188@shell0.pdx.osdl.net>
+Subject: shmat: stop mprotect from giving write permission to a readonly attachment (CVE-2006-1524)
+To: greg@kroah.com
+Cc: chrisw@sous-sol.org, akpm@osdl.org, hugh@veritas.com, stable@kernel.org
+From: akpm@osdl.org
+Date: Wed, 12 Apr 2006 14:34:27 -0700
+
+
+From: Hugh Dickins <hugh@veritas.com>
+
+I found that all of 2.4 and 2.6 have been letting mprotect give write
+permission to a readonly attachment of shared memory, whether or not IPC
+would give the caller that permission.
+
+SUS says "The behaviour of this function [mprotect] is unspecified if the
+mapping was not established by a call to mmap", but I don't think we can
+interpret that as allowing it to subvert IPC permissions.
+
+I haven't tried 2.2, but the 2.2.26 source looks like it gets it right; and
+the patch below reproduces that behaviour - mprotect cannot be used to add
+write permission to a shared memory segment attached readonly.
+
+This patch is simple, and I'm sure it's what we should have done in 2.4.0:
+if you want to go on to switch write permission on and off with mprotect,
+just don't attach the segment readonly in the first place.
+
+However, we could have accumulated apps which attach readonly (even though
+they would be permitted to attach read/write), and which subsequently use
+mprotect to switch write permission on and off: it's not unreasonable.
+
+I was going to add a second ipcperms check in do_shmat, to check for
+writable when readonly, and if not writable find_vma and clear VM_MAYWRITE.
+ But security_ipc_permission might do auditing, and it seems wrong to
+report an attempt for write permission when there has been none.  Or we
+could flag the vma as SHM, note the shmid or shp in vm_private_data, and
+then get mprotect to check.
+
+But the patch below is a lot simpler: I'd rather stick with it, if we can
+convince ourselves somehow that it'll be safe.
+
+Signed-off-by: Hugh Dickins <hugh@veritas.com>
+Signed-off-by: Andrew Morton <akpm@osdl.org>
+Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
+
+---
+ ipc/shm.c |    2 ++
+ 1 file changed, 2 insertions(+)
+
+--- linux-2.6.16.5.orig/ipc/shm.c
++++ linux-2.6.16.5/ipc/shm.c
+@@ -161,6 +161,8 @@ static int shm_mmap(struct file * file, 
+       ret = shmem_mmap(file, vma);
+       if (ret == 0) {
+               vma->vm_ops = &shm_vm_ops;
++              if (!(vma->vm_flags & VM_WRITE))
++                      vma->vm_flags &= ~VM_MAYWRITE;
+               shm_inc(file->f_dentry->d_inode->i_ino);
+       }