From: Dmitry Vyukov <dvyukov@google.com>
To: Al Viro <viro@zeniv.linux.org.uk>
Cc: "linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
syzkaller <syzkaller@googlegroups.com>
Subject: Re: fs: use-after-free in path_lookupat
Date: Thu, 23 Mar 2017 15:17:21 +0100 [thread overview]
Message-ID: <CACT4Y+byghFT+RVGoP9-osQYQfgujLmLGiFfBiR1oQ2Gfqf9TQ@mail.gmail.com> (raw)
In-Reply-To: <20170305191802.GK29622@ZenIV.linux.org.uk>
On Sun, Mar 5, 2017 at 8:18 PM, Al Viro <viro@zeniv.linux.org.uk> wrote:
> On Sun, Mar 05, 2017 at 06:33:18PM +0100, Dmitry Vyukov wrote:
>
>> Added more debug output.
>>
>> name_to_handle_at(r4, &(0x7f0000003000-0x6)="2e2f62757300",
>> &(0x7f0000003000-0xd)={0xc, 0x0, "cd21"}, &(0x7f0000002000)=0x0,
>> 0x1000)
>>
>> actually passes name="" because of the overlapping addresses. Flags
>> contain AT_EMPTY_PATH.
>
> Bloody hell... So you end up with name == (char *)&handle->handle_type + 3?
> Looks like it would be a lot more useful to dump the actual contents of
> those suckers right before the syscall...
>
> Anyway, that explains WTF is going on. The bug is in path_init() and
> it triggers when you pass something with dentry allocated by d_alloc_pseudo()
> as dfd, combined with empty pathname. You need to have the file closed
> by another thread, and have that another thread get out of closing syscall
> (close(), dup2(), etc.) before the caller of path_init() gets to
> complete_walk(). We need to make sure that this sucker gets DCACHE_RCUPDATE
> while it's still guaranteed to be pinned down. Could you try to reproduce
> with the patch below applied?
>
> diff --git a/fs/namei.c b/fs/namei.c
> index 6f7d96368734..70840281a41c 100644
> --- a/fs/namei.c
> +++ b/fs/namei.c
> @@ -2226,11 +2226,16 @@ static const char *path_init(struct nameidata *nd, unsigned flags)
> nd->path = f.file->f_path;
> if (flags & LOOKUP_RCU) {
> rcu_read_lock();
> - nd->inode = nd->path.dentry->d_inode;
> - nd->seq = read_seqcount_begin(&nd->path.dentry->d_seq);
> + if (unlikely(!(dentry->d_flags & DCACHE_RCUACCESS))) {
> + spin_lock(&dentry->d_lock);
> + dentry->d_flags |= DCACHE_RCUACCESS;
> + spin_unlock(&dentry->d_lock);
> + }
> + nd->inode = dentry->d_inode;
> + nd->seq = read_seqcount_begin(&dentry->d_seq);
> } else {
> path_get(&nd->path);
> - nd->inode = nd->path.dentry->d_inode;
> + nd->inode = dentry->d_inode;
> }
> fdput(f);
> return s;
Al, please send this patch officially. I am running with it since then
and have not seen the crashes, nor any other issues that look related.
Thanks!
next prev parent reply other threads:[~2017-03-23 14:17 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-04 14:59 fs: use-after-free in path_lookupat Dmitry Vyukov
2017-03-04 19:39 ` Al Viro
2017-03-05 11:15 ` Dmitry Vyukov
2017-03-05 11:20 ` Dmitry Vyukov
2017-03-05 11:24 ` Dmitry Vyukov
2017-03-05 11:37 ` Dmitry Vyukov
2017-03-05 15:57 ` Al Viro
2017-03-05 16:14 ` Dmitry Vyukov
2017-03-05 16:33 ` Al Viro
2017-03-05 17:33 ` Dmitry Vyukov
2017-03-05 17:38 ` Dmitry Vyukov
2017-03-05 19:18 ` Al Viro
2017-03-06 9:46 ` Dmitry Vyukov
2017-03-23 14:17 ` Dmitry Vyukov [this message]
2017-04-28 6:19 ` Dmitry Vyukov
2017-05-29 14:48 ` Dmitry Vyukov
2017-05-30 6:24 ` Al Viro
2017-05-30 8:19 ` Dmitry Vyukov
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=CACT4Y+byghFT+RVGoP9-osQYQfgujLmLGiFfBiR1oQ2Gfqf9TQ@mail.gmail.com \
--to=dvyukov@google.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=syzkaller@googlegroups.com \
--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).