From: Vitaliy Gusev <gusev.vitaliy@nexenta.com>
To: Trond Myklebust <Trond.Myklebust@netapp.com>,
Al Viro <viro@zeniv.linux.org.uk>
Cc: linux-fsdevel <linux-fsdevel@vger.kernel.org>,
David Howells <dhowells@redhat.com>,
linux-nfs@vger.kernel.org
Subject: [PATCH 0/2] nfsv4: Fix two remote DOS vulnerabilities v2
Date: Thu, 10 Feb 2011 14:54:54 +0300 [thread overview]
Message-ID: <1297338894.3667.0.camel@vT510> (raw)
Hello!
Next patches fix two NFSv4 client vulnerabilities.
First (memory corruption) can be raises anytime whereas second
(dereference ->lookup and call NULL pointer) can be raised during mount.
Repeatability 100%
--
Thanks,
Vitaliy Gusev
next reply other threads:[~2011-02-10 12:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-10 11:54 Vitaliy Gusev [this message]
2011-02-10 12:13 ` [PATCH 1/2] Fix memory corruption due to not expected FS_LOCATION Vitaliy Gusev
2011-02-10 12:21 ` [PATCH 2/2] nfsv4: Fix dereference i_op->lookup and call NULL pointer at d_alloc_and_lookup() Vitaliy Gusev
2011-03-21 17:34 ` [PATCH] Fix memory corruption due to not expected FS_LOCATIONS v3 Vitaliy Gusev
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=1297338894.3667.0.camel@vT510 \
--to=gusev.vitaliy@nexenta.com \
--cc=Trond.Myklebust@netapp.com \
--cc=dhowells@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
/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).