summaryrefslogtreecommitdiffstats
path: root/retired/CVE-2010-4161
diff options
context:
space:
mode:
authorMoritz Muehlenhoff <jmm@debian.org>2011-01-12 19:45:55 +0000
committerMoritz Muehlenhoff <jmm@debian.org>2011-01-12 19:45:55 +0000
commit66b8a9fb5af82cdb2d7716a18c121846bde265f1 (patch)
treeb066947ac6f758e4e704a61cd27433529f692186 /retired/CVE-2010-4161
parent5c884f446e8442183599431ba0b20c364f71d283 (diff)
retire issues
git-svn-id: svn+ssh://svn.debian.org/svn/kernel-sec@2136 e094ebfe-e918-0410-adfb-c712417f3574
Diffstat (limited to 'retired/CVE-2010-4161')
-rw-r--r--retired/CVE-2010-416118
1 files changed, 18 insertions, 0 deletions
diff --git a/retired/CVE-2010-4161 b/retired/CVE-2010-4161
new file mode 100644
index 00000000..f14e3edb
--- /dev/null
+++ b/retired/CVE-2010-4161
@@ -0,0 +1,18 @@
+Candidate: CVE-2010-4161
+Description:
+References:
+ https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2010-4161
+Notes:
+ jmm> The referenced patch ended up in 2.6.26.6, which was
+ jmm> pulled into the Lenny package. I find the statement in
+ jmm> https://bugzilla.redhat.com/show_bug.cgi?id=652534#c4
+ jmm> a bit confusing, why should RHEL6 have backported
+ jmm> fda9ef5d, the commit is from 2006?
+ jmm> Marking 2.6.27 as fixed upstream, since it includes
+ jmm> 93821778
+Bugs:
+upstream: released (2.6.27)
+2.6.32-upstream-stable: N/A
+linux-2.6: released (2.6.28-1)
+2.6.26-lenny-security: N/A "already have rcu protection; reproducer fails"
+2.6.32-squeeze-security: N/A

© 2014-2024 Faster IT GmbH | imprint | privacy policy