diff options
| author | dann frazier <dannf@debian.org> | 2006-08-17 00:24:25 +0000 |
|---|---|---|
| committer | dann frazier <dannf@debian.org> | 2006-08-17 00:24:25 +0000 |
| commit | f3581ec9b2d48c6103c22fecb46f713217d834e8 (patch) | |
| tree | 16359328df8385089d75b771a15c849bc9d052ea /retired/CVE-2006-1055 | |
| parent | fcaf6d1f99829e04e46b5eb27e1aac3451308455 (diff) | |
move retired to the top level hierarchy so people can easily checkout just the active issues
git-svn-id: svn+ssh://svn.debian.org/svn/kernel-sec@548 e094ebfe-e918-0410-adfb-c712417f3574
Diffstat (limited to 'retired/CVE-2006-1055')
| -rw-r--r-- | retired/CVE-2006-1055 | 26 |
1 files changed, 26 insertions, 0 deletions
diff --git a/retired/CVE-2006-1055 b/retired/CVE-2006-1055 new file mode 100644 index 00000000..3b264a56 --- /dev/null +++ b/retired/CVE-2006-1055 @@ -0,0 +1,26 @@ +Candidate: CVE-2006-1055 +References: +Description: + Quoting Greg KH: + Al just pointed me at an old sysfs patch that went into the tree last + year that has some potential security problems. Turns out that if you + write to a sysfs file exactly PAGE_SIZE worth of data, with no zeros in + it, there's a good chance you could read off the end of the kernel + buffer into who knows where. +Notes: + jmm> This was judged non-exploitable by Al Viro, but it's still a local DoS + jmm> 2.4 N/A, as it doesn't have sysfs + . + troyh> N/A for sarge, it was broken in 2.6.12 - 2.6.17-rc1. 2.6.8 is fine, + and since its's sysfs 2.4 is N/A. +Bugs: +upstream: released (2.6.17-rc1), released (2.6.16.2) +linux-2.6: released (2.6.16-6) +2.6.8-sarge-security: N/A +2.4.27-sarge-security: N/A +2.4.19-woody-security: N/A +2.4.18-woody-security: N/A +2.4.17-woody-security: N/A +2.4.16-woody-security: N/A +2.4.17-woody-security-hppa: N/A +2.4.17-woody-security-ia64: N/A |