diff options
| author | Moritz Muehlenhoff <jmm@debian.org> | 2008-02-22 21:53:05 +0000 |
|---|---|---|
| committer | Moritz Muehlenhoff <jmm@debian.org> | 2008-02-22 21:53:05 +0000 |
| commit | 0394957db79db8afcae11908388c24464b8d744f (patch) | |
| tree | 8f82b84cda898d89f438bc4c4e7b00e8d0324b60 /retired/CVE-2007-4311 | |
| parent | 60e5f903d389fc77fb16d492f07f52e65c20be16 (diff) | |
retire some issues
git-svn-id: svn+ssh://svn.debian.org/svn/kernel-sec@1140 e094ebfe-e918-0410-adfb-c712417f3574
Diffstat (limited to 'retired/CVE-2007-4311')
| -rw-r--r-- | retired/CVE-2007-4311 | 19 |
1 files changed, 19 insertions, 0 deletions
diff --git a/retired/CVE-2007-4311 b/retired/CVE-2007-4311 new file mode 100644 index 00000000..d4788e39 --- /dev/null +++ b/retired/CVE-2007-4311 @@ -0,0 +1,19 @@ +Candidate: CVE-2007-4311 +References: + http://git.kernel.org/?p=linux/kernel/git/wtarreau/linux-2.4.git;a=commitdiff_plain;h=66438bd5651e892bc485c32762f7ce75637b686b +Description: +Ubuntu-Description: +Notes: + dannf> The reporter noted that this is fixed in current 2.6's. It does + dannf> appear that way in Debian's 2.6.8 and 2.6.18, but the code that + dannf> solves it is quite a bit different in both. I wouldn't necessarily + dannf> assume that kernels between 2.6.8 & 2.6.18 are invulnerable. +Bugs: +upstream: released (2.4.35-rc1) +linux-2.6: N/A +2.6.18-etch-security: N/A +2.6.8-sarge-security: N/A +2.4.27-sarge-security: released (2.4.27-10sarge6) [248_random-reseed-sizeof-fix.diff] +2.6.15-dapper-security: N/A +2.6.17-edgy-security: N/A +2.6.20-feisty-security: N/A |