retire more issues

git-svn-id: svn+ssh://svn.debian.org/svn/kernel-sec@1530 e094ebfe-e918-0410-adfb-c712417f3574

1 files changed, 31 insertions, 0 deletions

diff --git a/retired/CVE-2009-0859 b/retired/CVE-2009-0859
new file mode 100644
index 00000000..15e2bb31
--- /dev/null
+++ b/retired/CVE-2009-0859
@@ -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: released (2.6.29-rc4)
+linux-2.6: released (2.6.29-1)
+2.6.18-etch-security: released (2.6.18.dfsg.1-24etch1) [bugfix/all/shm-fix-shmctl-SHM_INFO-lockup-without-CONFIG_SHMEM.patch]
+2.6.24-etch-security: released (2.6.24-6~etchnhalf.8etch1) [bugfix/all/shm-fix-shmctl-SHM_INFO-lockup-without-CONFIG_SHMEM.patch]
+2.6.26-lenny-security: released (2.6.26-15lenny1) [bugfix/all/shm-fix-shmctl-SHM_INFO-lockup-without-CONFIG_SHMEM.patch]
+2.6.15-dapper-security:
+2.6.22-gutsy-security:
+2.6.24-hardy-security:
+2.6.27-intrepid-security: