linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Valerie Aurora <vaurora@redhat.com>
To: Miklos Szeredi <miklos@szeredi.hu>
Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
	neilb@suse.de, viro@zeniv.linux.org.uk, stable@kernel.org
Subject: Re: [PATCH 5/7 v3] vfs: fix possible use after free in finish_open()
Date: Thu, 23 Sep 2010 16:19:19 -0400	[thread overview]
Message-ID: <20100923201919.GC3536@shell> (raw)
In-Reply-To: <20100920180446.104998543@szeredi.hu>

On Mon, Sep 20, 2010 at 08:04:09PM +0200, Miklos Szeredi wrote:
> From: Miklos Szeredi <mszeredi@suse.cz>
> 
> If open(O_TRUNC) is called and the actual open fails, then nd->path
> will be released by nameidata_to_filp().  If this races with an
> unmount then mnt_drop_write() can Oops.
> 
> Fix by acquiring a ref to nd->path and releasing after
> mnt_drop_write().
> 
> Signed-off-by: Miklos Szeredi <mszeredi@suse.cz>
> CC: stable@kernel.org
> ---
>  fs/namei.c |    9 ++++++++-
>  1 file changed, 8 insertions(+), 1 deletion(-)
> 
> Index: linux-2.6/fs/namei.c
> ===================================================================
> --- linux-2.6.orig/fs/namei.c	2010-09-20 13:32:35.000000000 +0200
> +++ linux-2.6/fs/namei.c	2010-09-20 13:33:14.000000000 +0200
> @@ -1559,6 +1559,11 @@ static struct file *finish_open(struct n
>  			mnt_drop_write(nd->path.mnt);
>  		goto exit;
>  	}
> +	if (will_truncate) {
> +		/* nameidata_to_filp() puts nd->path! */
> +		path_get(&nd->path);
> +	}
> +
>  	filp = nameidata_to_filp(nd);
>  	if (!IS_ERR(filp)) {
>  		error = ima_file_check(filp, acc_mode);
> @@ -1581,8 +1586,10 @@ static struct file *finish_open(struct n
>  	 * because the filp has had a write taken
>  	 * on its behalf.
>  	 */
> -	if (will_truncate)
> +	if (will_truncate) {
>  		mnt_drop_write(nd->path.mnt);
> +		path_put(&nd->path);
> +	}
>  	return filp;
>  
>  exit:
> 

Nice catch!

Reviewed-by: Valerie Aurora <vaurora@redhat.com>

-VAL

  reply	other threads:[~2010-09-23 20:19 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-20 18:04 [PATCH 0/7 v3] overlay filesystem prototype Miklos Szeredi
2010-09-20 18:04 ` [PATCH 1/7 v3] vfs: implement open "forwarding" Miklos Szeredi
2010-09-20 18:04 ` [PATCH 2/7 v3] vfs: make i_op->permission take a dentry instead of an inode Miklos Szeredi
2010-09-20 18:04 ` [PATCH 3/7 v3] vfs: add flag to allow rename to same inode Miklos Szeredi
2010-09-23 22:04   ` Valerie Aurora
2010-09-20 18:04 ` [PATCH 4/7 v3] vfs: export do_splice_direct() to modules Miklos Szeredi
2010-09-20 18:04 ` [PATCH 5/7 v3] vfs: fix possible use after free in finish_open() Miklos Szeredi
2010-09-23 20:19   ` Valerie Aurora [this message]
2010-09-20 18:04 ` [PATCH 6/7 v3] overlay: hybrid overlay filesystem prototype Miklos Szeredi
2010-09-22 23:21   ` Valerie Aurora
2010-09-24 14:33     ` Jens Axboe
2010-09-24 17:16       ` Valerie Aurora
2010-09-24 17:56   ` Valerie Aurora
2010-09-27  8:11     ` Miklos Szeredi
2010-09-27 11:49       ` Andreas Gruenbacher
2010-09-27 12:15         ` J. R. Okajima
2010-09-27 18:47       ` Valerie Aurora
2010-09-28  8:24         ` Andreas Gruenbacher
2010-09-30 21:51           ` Valerie Aurora
2010-10-01  9:34             ` Andreas Gruenbacher
2010-10-06 17:31               ` Valerie Aurora
2010-10-11  9:41                 ` Michal Suchanek
2010-10-11 13:51                 ` Scott James Remnant
2010-09-20 18:04 ` [PATCH 7/7 v3] overlay: overlay filesystem documentation Miklos Szeredi
2010-09-21  1:31 ` [PATCH 0/7 v3] overlay filesystem prototype Neil Brown
2010-09-22  9:50   ` Miklos Szeredi

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=20100923201919.GC3536@shell \
    --to=vaurora@redhat.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=miklos@szeredi.hu \
    --cc=neilb@suse.de \
    --cc=stable@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).