[kernel-sec-discuss] r1077 - active retired

[jmm at alioth.debian.org]

Author: jmm
Date: 2007-12-29 15:13:54 +0000 (Sat, 29 Dec 2007)
New Revision: 1077

Added:
   retired/CVE-2007-5501
   retired/CVE-2007-5908
Removed:
   active/CVE-2007-5501
   active/CVE-2007-5908
Log:
retire two issues


Deleted: active/CVE-2007-5501
===================================================================
--- active/CVE-2007-5501	2007-12-29 14:42:13 UTC (rev 1076)
+++ active/CVE-2007-5501	2007-12-29 15:13:54 UTC (rev 1077)
@@ -1,22 +0,0 @@
-Candidate: CVE-2007-5501
-References: 
- http://git.kernel.org/git/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=96a2d41a3e495734b63bff4e5dd0112741b93b38
-Description: 
-Ubuntu-Description: 
- Ilpo Järvinen discovered that it might be possible for the TCP stack
- to panic the kernel when receiving a crafted ACK response.  Only Ubuntu
- 7.10 contained the vulnerable code, and it is believed not to have
- been exploitable.
-Notes: 
- dannf> Jan Lieskovsky pointed out that tcp_write_queue_head() was introduced
- dannf> in 2.6.21-git1
-Bugs: 
-upstream: released (2.6.24-rc3), released (2.6.23.8)
-linux-2.6: released (2.6.23-1)
-2.6.18-etch-security: N/A
-2.6.8-sarge-security: N/A
-2.4.27-sarge-security: N/A
-2.6.15-dapper-security: N/A
-2.6.17-edgy-security: N/A
-2.6.20-feisty-security: N/A
-2.6.22-gutsy-security: released (2.6.22-14.47)

Deleted: active/CVE-2007-5908
===================================================================
--- active/CVE-2007-5908	2007-12-29 14:42:13 UTC (rev 1076)
+++ active/CVE-2007-5908	2007-12-29 15:13:54 UTC (rev 1077)
@@ -1,22 +0,0 @@
-Candidate: CVE-2007-5908
-Description: 
- *REJECTED*
- Buffer overflow in the (1) sysfs_show_available_clocksources and (2)
- sysfs_show_current_clocksources functions in Linux kernel 2.6.23 and earlier
- might allow local users to cause a denial of service or execute arbitrary
- code via crafted clock source names.
-References: 
- http://marc.info/?l=linux-kernel&m=119451922608530&w=2
-Ubuntu-Description: 
-Notes: 
- kees> this is not actually an exploitable security issue. there is no way to add clock sources that could trigger the overflow.
-Bugs: 
-upstream: N/A
-linux-2.6: N/A
-2.6.18-etch-security: N/A
-2.6.8-sarge-security: N/A
-2.4.27-sarge-security: N/A
-2.6.15-dapper-security: N/A
-2.6.17-edgy-security: N/A
-2.6.20-feisty-security: N/A
-2.6.22-gutsy-security: N/A

Copied: retired/CVE-2007-5501 (from rev 1075, active/CVE-2007-5501)
===================================================================
--- retired/CVE-2007-5501	                        (rev 0)
+++ retired/CVE-2007-5501	2007-12-29 15:13:54 UTC (rev 1077)
@@ -0,0 +1,22 @@
+Candidate: CVE-2007-5501
+References: 
+ http://git.kernel.org/git/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=96a2d41a3e495734b63bff4e5dd0112741b93b38
+Description: 
+Ubuntu-Description: 
+ Ilpo Järvinen discovered that it might be possible for the TCP stack
+ to panic the kernel when receiving a crafted ACK response.  Only Ubuntu
+ 7.10 contained the vulnerable code, and it is believed not to have
+ been exploitable.
+Notes: 
+ dannf> Jan Lieskovsky pointed out that tcp_write_queue_head() was introduced
+ dannf> in 2.6.21-git1
+Bugs: 
+upstream: released (2.6.24-rc3), released (2.6.23.8)
+linux-2.6: released (2.6.23-1)
+2.6.18-etch-security: N/A
+2.6.8-sarge-security: N/A
+2.4.27-sarge-security: N/A
+2.6.15-dapper-security: N/A
+2.6.17-edgy-security: N/A
+2.6.20-feisty-security: N/A
+2.6.22-gutsy-security: released (2.6.22-14.47)

Copied: retired/CVE-2007-5908 (from rev 1075, active/CVE-2007-5908)
===================================================================
--- retired/CVE-2007-5908	                        (rev 0)
+++ retired/CVE-2007-5908	2007-12-29 15:13:54 UTC (rev 1077)
@@ -0,0 +1,22 @@
+Candidate: CVE-2007-5908
+Description: 
+ *REJECTED*
+ Buffer overflow in the (1) sysfs_show_available_clocksources and (2)
+ sysfs_show_current_clocksources functions in Linux kernel 2.6.23 and earlier
+ might allow local users to cause a denial of service or execute arbitrary
+ code via crafted clock source names.
+References: 
+ http://marc.info/?l=linux-kernel&m=119451922608530&w=2
+Ubuntu-Description: 
+Notes: 
+ kees> this is not actually an exploitable security issue. there is no way to add clock sources that could trigger the overflow.
+Bugs: 
+upstream: N/A
+linux-2.6: N/A
+2.6.18-etch-security: N/A
+2.6.8-sarge-security: N/A
+2.4.27-sarge-security: N/A
+2.6.15-dapper-security: N/A
+2.6.17-edgy-security: N/A
+2.6.20-feisty-security: N/A
+2.6.22-gutsy-security: N/A