[kernel-sec-discuss] r1110 - active retired
dannf at alioth.debian.org
dannf at alioth.debian.org
Mon Jan 28 23:27:20 UTC 2008
Author: dannf
Date: 2008-01-28 23:27:20 +0000 (Mon, 28 Jan 2008)
New Revision: 1110
Added:
retired/CVE-2005-1763
Removed:
active/CVE-2005-1763
Log:
mark as x86_64 specific and retire
Deleted: active/CVE-2005-1763
===================================================================
--- active/CVE-2005-1763 2008-01-22 16:14:23 UTC (rev 1109)
+++ active/CVE-2005-1763 2008-01-28 23:27:20 UTC (rev 1110)
@@ -1,17 +0,0 @@
-Candidate: CVE-2005-1763
-References:
- http://www.novell.com/linux/security/advisories/2005_29_kernel.html
-Description:
- Buffer overflow in ptrace in the Linux Kernel for 64-bit architectures allows
- local users to write bytes into kernel memory.
-Notes:
- dannf> The patch we have is only for x86_64. This code was very different
- dannf> in 2.4, and we don't ship 2.4/amd64, so we can probably drop this one.
- dannf> The question is, does this affect other 64-bit archs?
-Bugs:
-upstream: released (2.6.12-rc5)
-linux-2.6: N/A
-2.6.8-sarge-security: released (2.6.8-16sarge1) [arch-x86_64-kernel-ptrace-boundary-check.dpatch]
-2.4.27-sarge-security: ignored (2.4.27-10sarge4)
-2.6.18-etch-security: N/A
-
Copied: retired/CVE-2005-1763 (from rev 1109, active/CVE-2005-1763)
===================================================================
--- retired/CVE-2005-1763 (rev 0)
+++ retired/CVE-2005-1763 2008-01-28 23:27:20 UTC (rev 1110)
@@ -0,0 +1,16 @@
+Candidate: CVE-2005-1763
+References:
+ http://www.novell.com/linux/security/advisories/2005_29_kernel.html
+Description:
+ Buffer overflow in ptrace in the Linux Kernel for 64-bit architectures allows
+ local users to write bytes into kernel memory.
+Notes:
+ dannf> The patch we have is only for x86_64. This code was very different
+ dannf> in 2.4, and we don't ship 2.4/amd64, so we can probably drop this one.
+Bugs:
+upstream: released (2.6.12-rc5)
+linux-2.6: N/A
+2.6.8-sarge-security: released (2.6.8-16sarge1) [arch-x86_64-kernel-ptrace-boundary-check.dpatch]
+2.4.27-sarge-security: ignored "no amd64/2.4 kernel"
+2.6.18-etch-security: N/A
+
More information about the kernel-sec-discuss
mailing list