retire several issues

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

1 files changed, 30 insertions, 0 deletions

diff --git a/retired/CVE-2006-5749 b/retired/CVE-2006-5749
new file mode 100644
index 00000000..0bfc2472
--- /dev/null
+++ b/retired/CVE-2006-5749
@@ -0,0 +1,30 @@
+Candidate: CVE-2006-5749
+References: 
+ http://www.kernel.org/git/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=dab6df63086762629936e8b89a5984bae39724f6
+Description: 
+ The isdn_ppp_ccp_reset_alloc_state function in
+ drivers/isdn/isdn_ppp.c in the Linux 2.4 kernel before 2.4.34-rc4
+ does not call the init_timer function for the ISDN PPP CCP reset
+ state timer, which has unknown attack vectors and results in a system
+ crash.
+Ubuntu-Description: 
+ Al Viro reported that the ISDN PPP module did not initialize the
+ reset state timer. By sending specially crafted ISDN packets, a
+ remote attacker could exploit this to crash the kernel.
+Notes: 
+ dannf> According to Marcel Holtmann, 2.4 and 2.6 < 2.6.13 are not vulnerable.
+ dannf> Indeed, in 2.4.27 & 2.6.8, init_timer() just sets timer->base to NULL,
+ dannf> so the memset() is sufficient to avoid this crash.
+ dannf> However, in 2.6.8 init_timer() also sets a magic number. add_timer()
+ dannf> will call __mod_timer(), which calls check_timer(), which will cause
+ dannf> the kernel to whine if this magic number is not set. I don't think this
+ dannf> will cause a crash, so I'm considering a non-security issue
+Bugs: 
+upstream: released (2.6.20-rc5)
+linux-2.6: released (2.6.20-1)
+2.6.18-etch-security: released (2.6.18.dfsg.1-10)
+2.6.8-sarge-security: N/A
+2.4.27-sarge-security: N/A
+2.6.12-breezy-security: released (2.6.12-10.43)
+2.6.15-dapper-security: released (2.6.15-28.51)
+2.6.17-edgy-security: released (2.6.17.1-11.35)