[kernel-sec-discuss] r1320 - active

[jmm at alioth.debian.org]

Author: jmm
Date: 2009-04-02 07:37:22 +0000 (Thu, 02 Apr 2009)
New Revision: 1320

Added:
   active/CVE-2009-0859
   active/CVE-2009-1046
Log:
new issues


Added: active/CVE-2009-0859
===================================================================
--- active/CVE-2009-0859	                        (rev 0)
+++ active/CVE-2009-0859	2009-04-02 07:37:22 UTC (rev 1320)
@@ -0,0 +1,31 @@
+Candidate: CVE-2009-0859
+Description:
+ The shm_get_stat function in ipc/shm.c in the shm subsystem
+ in the Linux kernel before 2.6.28.5, when CONFIG_SHMEM is
+ disabled, misinterprets the data type of an inode, which allows
+ local users to cause a denial of service (system hang) via
+ an SHM_INFO shmctl call, as demonstrated by running the ipcs
+ program. 
+References:
+ http://marc.info/?l=git-commits-head&m=123387479500599&w=2
+ http://marc.info/?l=linux-kernel&m=120428209704324&w=2
+ http://marc.info/?l=linux-kernel&m=123309645625549&w=2
+ http://openwall.com/lists/oss-security/2009/03/06/1
+ http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=a68e61e8ff2d46327a37b69056998b47745db6fa
+ http://kernel.org/pub/linux/kernel/v2.6/ChangeLog-2.6.28.5
+ http://patchwork.kernel.org/patch/6554/ 
+Ubuntu-Description:
+Notes:
+ jmm> All Debian kernels set CONFIG_SHMEM, so this is moot except
+ jmm> for locally modified configs and even for that I fail to
+ jmm> see why anyone would run a kernel w/o CONFIG_SHMEM?
+Bugs:
+upstream:
+linux-2.6:
+2.6.18-etch-security:
+2.6.24-etch-security:
+2.6.26-lenny-security:
+2.6.15-dapper-security:
+2.6.22-gutsy-security:
+2.6.24-hardy-security:
+2.6.27-intrepid-security:

Added: active/CVE-2009-1046
===================================================================
--- active/CVE-2009-1046	                        (rev 0)
+++ active/CVE-2009-1046	2009-04-02 07:37:22 UTC (rev 1320)
@@ -0,0 +1,28 @@
+Candidate: CVE-2009-1046
+Description:
+ The console selection feature in the Linux kernel 2.6.28 before
+ 2.6.28.4, 2.6.25, and possibly earlier versions, when the UTF-8
+ console is used, allows physically proximate attackers to cause
+ a denial of service (memory corruption) by selecting a small
+ number of 3-byte UTF-8 characters, which triggers an "an
+ off-by-two memory error." NOTE: it is not clear whether this issue
+ crosses privilege boundaries. 
+References:
+ http://lists.openwall.net/linux-kernel/2009/01/30/333
+ http://lists.openwall.net/linux-kernel/2009/02/02/364
+ http://www.openwall.com/lists/oss-security/2009/02/12/10
+ http://www.openwall.com/lists/oss-security/2009/02/12/11
+ http://www.openwall.com/lists/oss-security/2009/02/12/9
+ http://www.kernel.org/pub/linux/kernel/v2.6/ChangeLog-2.6.28.4 
+Ubuntu-Description:
+Notes:
+Bugs:
+upstream: released (2.6.28.4)
+linux-2.6: released (2.6.29-1)
+2.6.18-etch-security:
+2.6.24-etch-security:
+2.6.26-lenny-security:
+2.6.15-dapper-security:
+2.6.22-gutsy-security:
+2.6.24-hardy-security:
+2.6.27-intrepid-security: