From: Majkls <majkls@tiscali.cz>
To: linux-fsdevel@vger.kernel.org
Subject: Unpatched secunia advisories
Date: Wed, 17 Jan 2007 18:56:06 +0100 [thread overview]
Message-ID: <45AE6336.7010503@tiscali.cz> (raw)
Hello,
some time ago I sent some open advisory there, but in fact it had been
already fixed. So I want to continue in this chase on open advisories
and closed bugs. So there is some from FS:
CVE-2006-2629 - Race condition in Linux kernel 2.6.15 to 2.6.17, when
running on SMP platforms, allows local users to cause a denial of
service (crash) by creating and exiting a large number of tasks, then
accessing the /proc entry of a task that is exiting, which causes memory
corruption that leads to a failure in the prune_dcache function or a
BUG_ON error in include/linux/list.h.
= What is status of this bug? (in all 2.6 forks)
I also suppose this bug has been fixed in all 2.6 branches allready:
CVE-2004-1235 (http://secunia.com/advisories/13756/)
What is status of this bug:
http://secunia.com/cve_reference/CVE-2004-1058/
This has been already fixed, hasn't it?
http://secunia.com/advisories/13126/
CVE-2004-1070, CVE-2004-1071, CVE-2004-1072, CVE-2004-1073
http://secunia.com/advisories/12426/ - Has already been this bug fixed?
http://secunia.com/advisories/12210/ - Linux Kernel File Offset Pointer
Handling Memory Disclosure Vulnerability. On secunia is that is fixed
only in 2.4.
If you want reply that have been already fixed, please attach link to
main git repository on kernel.org.
--
Miloslav "Majkls" Semler
reply other threads:[~2007-01-17 18:17 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=45AE6336.7010503@tiscali.cz \
--to=majkls@tiscali.cz \
--cc=linux-fsdevel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).