[kernel-sec-discuss] r1687 - active ignored
Moritz Muehlenhoff
jmm at alioth.debian.org
Sun Jan 31 11:37:57 UTC 2010
Author: jmm
Date: 2010-01-31 11:37:57 +0000 (Sun, 31 Jan 2010)
New Revision: 1687
Added:
ignored/CVE-2006-6921
ignored/CVE-2006-7051
Removed:
active/CVE-2006-6921
active/CVE-2006-7051
Log:
ignore two ancient issues
Deleted: active/CVE-2006-6921
===================================================================
--- active/CVE-2006-6921 2010-01-31 11:32:49 UTC (rev 1686)
+++ active/CVE-2006-6921 2010-01-31 11:37:57 UTC (rev 1687)
@@ -1,24 +0,0 @@
-Candidate: CVE-2006-6921
-References:
- http://uwsg.iu.edu/hypermail/linux/kernel/0612.2/0980.html
- http://uwsg.iu.edu/hypermail/linux/kernel/0612.2/1021.html
-Description:
- Unspecified versions of the Linux kernel allows local users to cause
- a denial of service (unrecoverable zombie process) via a program with
- certain instructions that prevent init from properly reaping a child
- whose parent has died.
-Ubuntu-Description:
-Notes:
- 2.4 behaves correctly
- dannf> unaware of an upstream fix
-Bugs:
-upstream:
-linux-2.6: ignored "no upstream fix"
-2.6.18-etch-security: ignored (2.6.18.dfsg.1-13etch6) "no upstream fix"
-2.6.24-etch-security: ignored "no upstream fix"
-2.6.26-lenny-security: ignored
-2.6.8-sarge-security: ignored (2.6.8-16sarge7)
-2.4.27-sarge-security: N/A
-2.6.15-dapper-security: ignored
-2.6.17-edgy-security: ignored - no upstream patch
-2.6.20-feisty-security: ignored
Deleted: active/CVE-2006-7051
===================================================================
--- active/CVE-2006-7051 2010-01-31 11:32:49 UTC (rev 1686)
+++ active/CVE-2006-7051 2010-01-31 11:37:57 UTC (rev 1687)
@@ -1,33 +0,0 @@
-Candidate: CVE-2006-7051
-References:
- BUGTRAQ:20060404 Linux Kernel Local DoS vulnerability.
- URL:http://www.securityfocus.com/archive/1/archive/1/430278/30/5790/threaded
- MILW0RM:1657
- URL:http://www.milw0rm.com/exploits/1657
- XF:linux-systimercreate-dos(25712)
- URL:http://xforce.iss.net/xforce/xfdb/25712
-Description:
- The sys_timer_create function in posix-timers.c for Linux kernel 2.6.x
- allows local users to cause a denial of service (memory consumption) and
- possibly bypass memory limits or cause other processes to be killed by
- creating a large number of posix timers, which are allocated in kernel
- memory but are not treated as part of the process' memory.
-Ubuntu-Description:
-Notes:
- dannf> Debian should probably "fix" this by suggesting a limit (ulimit -i)
- on the number of pending signals
- kees> Pending signals limit is now set by pam 0.99.x.
- jmm> d02479bdeb1c9b037892061cdcf4e730183391fa
- dannf> The milw0rm exploit seems to still work on 2.6.24, so I don't think
- the d02479b changeset changed this behavior.
-Bugs:
-upstream: released (2.6.23-rc4)
-linux-2.6: released (2.6.23-1)
-2.6.18-etch-security: ignored (2.6.18.dfsg.1-13etch6) "no upstream patch"
-2.6.24-etch-security: ignored "no upstream patch"
-2.6.26-lenny-security: ignored "no upstream patch"
-2.6.8-sarge-security: ignored (2.6.8-17sarge1) "no upstream patch"
-2.4.27-sarge-security: N/A "No posix-timers.c"
-2.6.15-dapper-security: ignore (no upstream patch)
-2.6.17-edgy-security: ignore (no upstream patch)
-2.6.20-feisty: ignore (no upstream patch)
Copied: ignored/CVE-2006-6921 (from rev 1686, active/CVE-2006-6921)
===================================================================
--- ignored/CVE-2006-6921 (rev 0)
+++ ignored/CVE-2006-6921 2010-01-31 11:37:57 UTC (rev 1687)
@@ -0,0 +1,24 @@
+Candidate: CVE-2006-6921
+References:
+ http://uwsg.iu.edu/hypermail/linux/kernel/0612.2/0980.html
+ http://uwsg.iu.edu/hypermail/linux/kernel/0612.2/1021.html
+Description:
+ Unspecified versions of the Linux kernel allows local users to cause
+ a denial of service (unrecoverable zombie process) via a program with
+ certain instructions that prevent init from properly reaping a child
+ whose parent has died.
+Ubuntu-Description:
+Notes:
+ 2.4 behaves correctly
+ dannf> unaware of an upstream fix
+Bugs:
+upstream:
+linux-2.6: ignored "no upstream fix"
+2.6.18-etch-security: ignored (2.6.18.dfsg.1-13etch6) "no upstream fix"
+2.6.24-etch-security: ignored "no upstream fix"
+2.6.26-lenny-security: ignored
+2.6.8-sarge-security: ignored (2.6.8-16sarge7)
+2.4.27-sarge-security: N/A
+2.6.15-dapper-security: ignored
+2.6.17-edgy-security: ignored - no upstream patch
+2.6.20-feisty-security: ignored
Copied: ignored/CVE-2006-7051 (from rev 1686, active/CVE-2006-7051)
===================================================================
--- ignored/CVE-2006-7051 (rev 0)
+++ ignored/CVE-2006-7051 2010-01-31 11:37:57 UTC (rev 1687)
@@ -0,0 +1,33 @@
+Candidate: CVE-2006-7051
+References:
+ BUGTRAQ:20060404 Linux Kernel Local DoS vulnerability.
+ URL:http://www.securityfocus.com/archive/1/archive/1/430278/30/5790/threaded
+ MILW0RM:1657
+ URL:http://www.milw0rm.com/exploits/1657
+ XF:linux-systimercreate-dos(25712)
+ URL:http://xforce.iss.net/xforce/xfdb/25712
+Description:
+ The sys_timer_create function in posix-timers.c for Linux kernel 2.6.x
+ allows local users to cause a denial of service (memory consumption) and
+ possibly bypass memory limits or cause other processes to be killed by
+ creating a large number of posix timers, which are allocated in kernel
+ memory but are not treated as part of the process' memory.
+Ubuntu-Description:
+Notes:
+ dannf> Debian should probably "fix" this by suggesting a limit (ulimit -i)
+ on the number of pending signals
+ kees> Pending signals limit is now set by pam 0.99.x.
+ jmm> d02479bdeb1c9b037892061cdcf4e730183391fa
+ dannf> The milw0rm exploit seems to still work on 2.6.24, so I don't think
+ the d02479b changeset changed this behavior.
+Bugs:
+upstream: released (2.6.23-rc4)
+linux-2.6: released (2.6.23-1)
+2.6.18-etch-security: ignored (2.6.18.dfsg.1-13etch6) "no upstream patch"
+2.6.24-etch-security: ignored "no upstream patch"
+2.6.26-lenny-security: ignored "no upstream patch"
+2.6.8-sarge-security: ignored (2.6.8-17sarge1) "no upstream patch"
+2.4.27-sarge-security: N/A "No posix-timers.c"
+2.6.15-dapper-security: ignore (no upstream patch)
+2.6.17-edgy-security: ignore (no upstream patch)
+2.6.20-feisty: ignore (no upstream patch)
More information about the kernel-sec-discuss
mailing list