2010-07-30 05:47:57 +08:00
|
|
|
/*
|
|
|
|
* AppArmor security module
|
|
|
|
*
|
|
|
|
* This file contains AppArmor function for pathnames
|
|
|
|
*
|
|
|
|
* Copyright (C) 1998-2008 Novell/SUSE
|
|
|
|
* Copyright 2009-2010 Canonical Ltd.
|
|
|
|
*
|
|
|
|
* This program is free software; you can redistribute it and/or
|
|
|
|
* modify it under the terms of the GNU General Public License as
|
|
|
|
* published by the Free Software Foundation, version 2 of the
|
|
|
|
* License.
|
|
|
|
*/
|
|
|
|
|
|
|
|
#include <linux/magic.h>
|
|
|
|
#include <linux/mount.h>
|
|
|
|
#include <linux/namei.h>
|
|
|
|
#include <linux/nsproxy.h>
|
|
|
|
#include <linux/path.h>
|
|
|
|
#include <linux/sched.h>
|
|
|
|
#include <linux/slab.h>
|
|
|
|
#include <linux/fs_struct.h>
|
|
|
|
|
|
|
|
#include "include/apparmor.h"
|
|
|
|
#include "include/path.h"
|
|
|
|
#include "include/policy.h"
|
|
|
|
|
|
|
|
|
|
|
|
/* modified from dcache.c */
|
|
|
|
static int prepend(char **buffer, int buflen, const char *str, int namelen)
|
|
|
|
{
|
|
|
|
buflen -= namelen;
|
|
|
|
if (buflen < 0)
|
|
|
|
return -ENAMETOOLONG;
|
|
|
|
*buffer -= namelen;
|
|
|
|
memcpy(*buffer, str, namelen);
|
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
|
|
|
#define CHROOT_NSCONNECT (PATH_CHROOT_REL | PATH_CHROOT_NSCONNECT)
|
|
|
|
|
|
|
|
/**
|
|
|
|
* d_namespace_path - lookup a name associated with a given path
|
|
|
|
* @path: path to lookup (NOT NULL)
|
|
|
|
* @buf: buffer to store path to (NOT NULL)
|
|
|
|
* @buflen: length of @buf
|
|
|
|
* @name: Returns - pointer for start of path name with in @buf (NOT NULL)
|
|
|
|
* @flags: flags controlling path lookup
|
|
|
|
*
|
|
|
|
* Handle path name lookup.
|
|
|
|
*
|
|
|
|
* Returns: %0 else error code if path lookup fails
|
|
|
|
* When no error the path name is returned in @name which points to
|
|
|
|
* to a position in @buf
|
|
|
|
*/
|
2016-03-26 02:18:14 +08:00
|
|
|
static int d_namespace_path(const struct path *path, char *buf, int buflen,
|
2010-07-30 05:47:57 +08:00
|
|
|
char **name, int flags)
|
|
|
|
{
|
|
|
|
char *res;
|
fix apparmor dereferencing potentially freed dentry, sanitize __d_path() API
__d_path() API is asking for trouble and in case of apparmor d_namespace_path()
getting just that. The root cause is that when __d_path() misses the root
it had been told to look for, it stores the location of the most remote ancestor
in *root. Without grabbing references. Sure, at the moment of call it had
been pinned down by what we have in *path. And if we raced with umount -l, we
could have very well stopped at vfsmount/dentry that got freed as soon as
prepend_path() dropped vfsmount_lock.
It is safe to compare these pointers with pre-existing (and known to be still
alive) vfsmount and dentry, as long as all we are asking is "is it the same
address?". Dereferencing is not safe and apparmor ended up stepping into
that. d_namespace_path() really wants to examine the place where we stopped,
even if it's not connected to our namespace. As the result, it looked
at ->d_sb->s_magic of a dentry that might've been already freed by that point.
All other callers had been careful enough to avoid that, but it's really
a bad interface - it invites that kind of trouble.
The fix is fairly straightforward, even though it's bigger than I'd like:
* prepend_path() root argument becomes const.
* __d_path() is never called with NULL/NULL root. It was a kludge
to start with. Instead, we have an explicit function - d_absolute_root().
Same as __d_path(), except that it doesn't get root passed and stops where
it stops. apparmor and tomoyo are using it.
* __d_path() returns NULL on path outside of root. The main
caller is show_mountinfo() and that's precisely what we pass root for - to
skip those outside chroot jail. Those who don't want that can (and do)
use d_path().
* __d_path() root argument becomes const. Everyone agrees, I hope.
* apparmor does *NOT* try to use __d_path() or any of its variants
when it sees that path->mnt is an internal vfsmount. In that case it's
definitely not mounted anywhere and dentry_path() is exactly what we want
there. Handling of sysctl()-triggered weirdness is moved to that place.
* if apparmor is asked to do pathname relative to chroot jail
and __d_path() tells it we it's not in that jail, the sucker just calls
d_absolute_path() instead. That's the other remaining caller of __d_path(),
BTW.
* seq_path_root() does _NOT_ return -ENAMETOOLONG (it's stupid anyway -
the normal seq_file logics will take care of growing the buffer and redoing
the call of ->show() just fine). However, if it gets path not reachable
from root, it returns SEQ_SKIP. The only caller adjusted (i.e. stopped
ignoring the return value as it used to do).
Reviewed-by: John Johansen <john.johansen@canonical.com>
ACKed-by: John Johansen <john.johansen@canonical.com>
Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
Cc: stable@vger.kernel.org
2011-12-05 21:43:34 +08:00
|
|
|
int error = 0;
|
|
|
|
int connected = 1;
|
2010-07-30 05:47:57 +08:00
|
|
|
|
fix apparmor dereferencing potentially freed dentry, sanitize __d_path() API
__d_path() API is asking for trouble and in case of apparmor d_namespace_path()
getting just that. The root cause is that when __d_path() misses the root
it had been told to look for, it stores the location of the most remote ancestor
in *root. Without grabbing references. Sure, at the moment of call it had
been pinned down by what we have in *path. And if we raced with umount -l, we
could have very well stopped at vfsmount/dentry that got freed as soon as
prepend_path() dropped vfsmount_lock.
It is safe to compare these pointers with pre-existing (and known to be still
alive) vfsmount and dentry, as long as all we are asking is "is it the same
address?". Dereferencing is not safe and apparmor ended up stepping into
that. d_namespace_path() really wants to examine the place where we stopped,
even if it's not connected to our namespace. As the result, it looked
at ->d_sb->s_magic of a dentry that might've been already freed by that point.
All other callers had been careful enough to avoid that, but it's really
a bad interface - it invites that kind of trouble.
The fix is fairly straightforward, even though it's bigger than I'd like:
* prepend_path() root argument becomes const.
* __d_path() is never called with NULL/NULL root. It was a kludge
to start with. Instead, we have an explicit function - d_absolute_root().
Same as __d_path(), except that it doesn't get root passed and stops where
it stops. apparmor and tomoyo are using it.
* __d_path() returns NULL on path outside of root. The main
caller is show_mountinfo() and that's precisely what we pass root for - to
skip those outside chroot jail. Those who don't want that can (and do)
use d_path().
* __d_path() root argument becomes const. Everyone agrees, I hope.
* apparmor does *NOT* try to use __d_path() or any of its variants
when it sees that path->mnt is an internal vfsmount. In that case it's
definitely not mounted anywhere and dentry_path() is exactly what we want
there. Handling of sysctl()-triggered weirdness is moved to that place.
* if apparmor is asked to do pathname relative to chroot jail
and __d_path() tells it we it's not in that jail, the sucker just calls
d_absolute_path() instead. That's the other remaining caller of __d_path(),
BTW.
* seq_path_root() does _NOT_ return -ENAMETOOLONG (it's stupid anyway -
the normal seq_file logics will take care of growing the buffer and redoing
the call of ->show() just fine). However, if it gets path not reachable
from root, it returns SEQ_SKIP. The only caller adjusted (i.e. stopped
ignoring the return value as it used to do).
Reviewed-by: John Johansen <john.johansen@canonical.com>
ACKed-by: John Johansen <john.johansen@canonical.com>
Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
Cc: stable@vger.kernel.org
2011-12-05 21:43:34 +08:00
|
|
|
if (path->mnt->mnt_flags & MNT_INTERNAL) {
|
|
|
|
/* it's not mounted anywhere */
|
|
|
|
res = dentry_path(path->dentry, buf, buflen);
|
|
|
|
*name = res;
|
|
|
|
if (IS_ERR(res)) {
|
|
|
|
*name = buf;
|
|
|
|
return PTR_ERR(res);
|
|
|
|
}
|
|
|
|
if (path->dentry->d_sb->s_magic == PROC_SUPER_MAGIC &&
|
|
|
|
strncmp(*name, "/sys/", 5) == 0) {
|
|
|
|
/* TODO: convert over to using a per namespace
|
|
|
|
* control instead of hard coded /proc
|
|
|
|
*/
|
|
|
|
return prepend(name, *name - buf, "/proc", 5);
|
|
|
|
}
|
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
|
|
|
/* resolve paths relative to chroot?*/
|
2010-07-30 05:47:57 +08:00
|
|
|
if (flags & PATH_CHROOT_REL) {
|
fix apparmor dereferencing potentially freed dentry, sanitize __d_path() API
__d_path() API is asking for trouble and in case of apparmor d_namespace_path()
getting just that. The root cause is that when __d_path() misses the root
it had been told to look for, it stores the location of the most remote ancestor
in *root. Without grabbing references. Sure, at the moment of call it had
been pinned down by what we have in *path. And if we raced with umount -l, we
could have very well stopped at vfsmount/dentry that got freed as soon as
prepend_path() dropped vfsmount_lock.
It is safe to compare these pointers with pre-existing (and known to be still
alive) vfsmount and dentry, as long as all we are asking is "is it the same
address?". Dereferencing is not safe and apparmor ended up stepping into
that. d_namespace_path() really wants to examine the place where we stopped,
even if it's not connected to our namespace. As the result, it looked
at ->d_sb->s_magic of a dentry that might've been already freed by that point.
All other callers had been careful enough to avoid that, but it's really
a bad interface - it invites that kind of trouble.
The fix is fairly straightforward, even though it's bigger than I'd like:
* prepend_path() root argument becomes const.
* __d_path() is never called with NULL/NULL root. It was a kludge
to start with. Instead, we have an explicit function - d_absolute_root().
Same as __d_path(), except that it doesn't get root passed and stops where
it stops. apparmor and tomoyo are using it.
* __d_path() returns NULL on path outside of root. The main
caller is show_mountinfo() and that's precisely what we pass root for - to
skip those outside chroot jail. Those who don't want that can (and do)
use d_path().
* __d_path() root argument becomes const. Everyone agrees, I hope.
* apparmor does *NOT* try to use __d_path() or any of its variants
when it sees that path->mnt is an internal vfsmount. In that case it's
definitely not mounted anywhere and dentry_path() is exactly what we want
there. Handling of sysctl()-triggered weirdness is moved to that place.
* if apparmor is asked to do pathname relative to chroot jail
and __d_path() tells it we it's not in that jail, the sucker just calls
d_absolute_path() instead. That's the other remaining caller of __d_path(),
BTW.
* seq_path_root() does _NOT_ return -ENAMETOOLONG (it's stupid anyway -
the normal seq_file logics will take care of growing the buffer and redoing
the call of ->show() just fine). However, if it gets path not reachable
from root, it returns SEQ_SKIP. The only caller adjusted (i.e. stopped
ignoring the return value as it used to do).
Reviewed-by: John Johansen <john.johansen@canonical.com>
ACKed-by: John Johansen <john.johansen@canonical.com>
Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
Cc: stable@vger.kernel.org
2011-12-05 21:43:34 +08:00
|
|
|
struct path root;
|
2010-08-18 02:37:32 +08:00
|
|
|
get_fs_root(current->fs, &root);
|
fix apparmor dereferencing potentially freed dentry, sanitize __d_path() API
__d_path() API is asking for trouble and in case of apparmor d_namespace_path()
getting just that. The root cause is that when __d_path() misses the root
it had been told to look for, it stores the location of the most remote ancestor
in *root. Without grabbing references. Sure, at the moment of call it had
been pinned down by what we have in *path. And if we raced with umount -l, we
could have very well stopped at vfsmount/dentry that got freed as soon as
prepend_path() dropped vfsmount_lock.
It is safe to compare these pointers with pre-existing (and known to be still
alive) vfsmount and dentry, as long as all we are asking is "is it the same
address?". Dereferencing is not safe and apparmor ended up stepping into
that. d_namespace_path() really wants to examine the place where we stopped,
even if it's not connected to our namespace. As the result, it looked
at ->d_sb->s_magic of a dentry that might've been already freed by that point.
All other callers had been careful enough to avoid that, but it's really
a bad interface - it invites that kind of trouble.
The fix is fairly straightforward, even though it's bigger than I'd like:
* prepend_path() root argument becomes const.
* __d_path() is never called with NULL/NULL root. It was a kludge
to start with. Instead, we have an explicit function - d_absolute_root().
Same as __d_path(), except that it doesn't get root passed and stops where
it stops. apparmor and tomoyo are using it.
* __d_path() returns NULL on path outside of root. The main
caller is show_mountinfo() and that's precisely what we pass root for - to
skip those outside chroot jail. Those who don't want that can (and do)
use d_path().
* __d_path() root argument becomes const. Everyone agrees, I hope.
* apparmor does *NOT* try to use __d_path() or any of its variants
when it sees that path->mnt is an internal vfsmount. In that case it's
definitely not mounted anywhere and dentry_path() is exactly what we want
there. Handling of sysctl()-triggered weirdness is moved to that place.
* if apparmor is asked to do pathname relative to chroot jail
and __d_path() tells it we it's not in that jail, the sucker just calls
d_absolute_path() instead. That's the other remaining caller of __d_path(),
BTW.
* seq_path_root() does _NOT_ return -ENAMETOOLONG (it's stupid anyway -
the normal seq_file logics will take care of growing the buffer and redoing
the call of ->show() just fine). However, if it gets path not reachable
from root, it returns SEQ_SKIP. The only caller adjusted (i.e. stopped
ignoring the return value as it used to do).
Reviewed-by: John Johansen <john.johansen@canonical.com>
ACKed-by: John Johansen <john.johansen@canonical.com>
Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
Cc: stable@vger.kernel.org
2011-12-05 21:43:34 +08:00
|
|
|
res = __d_path(path, &root, buf, buflen);
|
|
|
|
path_put(&root);
|
2012-02-16 22:32:47 +08:00
|
|
|
} else {
|
2012-02-16 22:21:30 +08:00
|
|
|
res = d_absolute_path(path, buf, buflen);
|
2012-02-16 22:32:47 +08:00
|
|
|
if (!our_mnt(path->mnt))
|
|
|
|
connected = 0;
|
|
|
|
}
|
2010-07-30 05:47:57 +08:00
|
|
|
|
|
|
|
/* handle error conditions - and still allow a partial path to
|
|
|
|
* be returned.
|
|
|
|
*/
|
2012-02-16 22:32:47 +08:00
|
|
|
if (!res || IS_ERR(res)) {
|
2012-05-17 02:01:05 +08:00
|
|
|
if (PTR_ERR(res) == -ENAMETOOLONG)
|
|
|
|
return -ENAMETOOLONG;
|
2012-02-16 22:32:47 +08:00
|
|
|
connected = 0;
|
2012-02-16 22:28:50 +08:00
|
|
|
res = dentry_path_raw(path->dentry, buf, buflen);
|
|
|
|
if (IS_ERR(res)) {
|
|
|
|
error = PTR_ERR(res);
|
|
|
|
*name = buf;
|
|
|
|
goto out;
|
|
|
|
};
|
|
|
|
} else if (!our_mnt(path->mnt))
|
fix apparmor dereferencing potentially freed dentry, sanitize __d_path() API
__d_path() API is asking for trouble and in case of apparmor d_namespace_path()
getting just that. The root cause is that when __d_path() misses the root
it had been told to look for, it stores the location of the most remote ancestor
in *root. Without grabbing references. Sure, at the moment of call it had
been pinned down by what we have in *path. And if we raced with umount -l, we
could have very well stopped at vfsmount/dentry that got freed as soon as
prepend_path() dropped vfsmount_lock.
It is safe to compare these pointers with pre-existing (and known to be still
alive) vfsmount and dentry, as long as all we are asking is "is it the same
address?". Dereferencing is not safe and apparmor ended up stepping into
that. d_namespace_path() really wants to examine the place where we stopped,
even if it's not connected to our namespace. As the result, it looked
at ->d_sb->s_magic of a dentry that might've been already freed by that point.
All other callers had been careful enough to avoid that, but it's really
a bad interface - it invites that kind of trouble.
The fix is fairly straightforward, even though it's bigger than I'd like:
* prepend_path() root argument becomes const.
* __d_path() is never called with NULL/NULL root. It was a kludge
to start with. Instead, we have an explicit function - d_absolute_root().
Same as __d_path(), except that it doesn't get root passed and stops where
it stops. apparmor and tomoyo are using it.
* __d_path() returns NULL on path outside of root. The main
caller is show_mountinfo() and that's precisely what we pass root for - to
skip those outside chroot jail. Those who don't want that can (and do)
use d_path().
* __d_path() root argument becomes const. Everyone agrees, I hope.
* apparmor does *NOT* try to use __d_path() or any of its variants
when it sees that path->mnt is an internal vfsmount. In that case it's
definitely not mounted anywhere and dentry_path() is exactly what we want
there. Handling of sysctl()-triggered weirdness is moved to that place.
* if apparmor is asked to do pathname relative to chroot jail
and __d_path() tells it we it's not in that jail, the sucker just calls
d_absolute_path() instead. That's the other remaining caller of __d_path(),
BTW.
* seq_path_root() does _NOT_ return -ENAMETOOLONG (it's stupid anyway -
the normal seq_file logics will take care of growing the buffer and redoing
the call of ->show() just fine). However, if it gets path not reachable
from root, it returns SEQ_SKIP. The only caller adjusted (i.e. stopped
ignoring the return value as it used to do).
Reviewed-by: John Johansen <john.johansen@canonical.com>
ACKed-by: John Johansen <john.johansen@canonical.com>
Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
Cc: stable@vger.kernel.org
2011-12-05 21:43:34 +08:00
|
|
|
connected = 0;
|
2010-07-30 05:47:57 +08:00
|
|
|
|
2012-02-16 22:28:50 +08:00
|
|
|
*name = res;
|
|
|
|
|
2010-08-28 09:33:26 +08:00
|
|
|
/* Handle two cases:
|
|
|
|
* 1. A deleted dentry && profile is not allowing mediation of deleted
|
|
|
|
* 2. On some filesystems, newly allocated dentries appear to the
|
|
|
|
* security_path hooks as a deleted dentry except without an inode
|
|
|
|
* allocated.
|
|
|
|
*/
|
2015-01-29 20:02:31 +08:00
|
|
|
if (d_unlinked(path->dentry) && d_is_positive(path->dentry) &&
|
2010-08-28 09:33:26 +08:00
|
|
|
!(flags & PATH_MEDIATE_DELETED)) {
|
2010-07-30 05:47:57 +08:00
|
|
|
error = -ENOENT;
|
|
|
|
goto out;
|
|
|
|
}
|
|
|
|
|
fix apparmor dereferencing potentially freed dentry, sanitize __d_path() API
__d_path() API is asking for trouble and in case of apparmor d_namespace_path()
getting just that. The root cause is that when __d_path() misses the root
it had been told to look for, it stores the location of the most remote ancestor
in *root. Without grabbing references. Sure, at the moment of call it had
been pinned down by what we have in *path. And if we raced with umount -l, we
could have very well stopped at vfsmount/dentry that got freed as soon as
prepend_path() dropped vfsmount_lock.
It is safe to compare these pointers with pre-existing (and known to be still
alive) vfsmount and dentry, as long as all we are asking is "is it the same
address?". Dereferencing is not safe and apparmor ended up stepping into
that. d_namespace_path() really wants to examine the place where we stopped,
even if it's not connected to our namespace. As the result, it looked
at ->d_sb->s_magic of a dentry that might've been already freed by that point.
All other callers had been careful enough to avoid that, but it's really
a bad interface - it invites that kind of trouble.
The fix is fairly straightforward, even though it's bigger than I'd like:
* prepend_path() root argument becomes const.
* __d_path() is never called with NULL/NULL root. It was a kludge
to start with. Instead, we have an explicit function - d_absolute_root().
Same as __d_path(), except that it doesn't get root passed and stops where
it stops. apparmor and tomoyo are using it.
* __d_path() returns NULL on path outside of root. The main
caller is show_mountinfo() and that's precisely what we pass root for - to
skip those outside chroot jail. Those who don't want that can (and do)
use d_path().
* __d_path() root argument becomes const. Everyone agrees, I hope.
* apparmor does *NOT* try to use __d_path() or any of its variants
when it sees that path->mnt is an internal vfsmount. In that case it's
definitely not mounted anywhere and dentry_path() is exactly what we want
there. Handling of sysctl()-triggered weirdness is moved to that place.
* if apparmor is asked to do pathname relative to chroot jail
and __d_path() tells it we it's not in that jail, the sucker just calls
d_absolute_path() instead. That's the other remaining caller of __d_path(),
BTW.
* seq_path_root() does _NOT_ return -ENAMETOOLONG (it's stupid anyway -
the normal seq_file logics will take care of growing the buffer and redoing
the call of ->show() just fine). However, if it gets path not reachable
from root, it returns SEQ_SKIP. The only caller adjusted (i.e. stopped
ignoring the return value as it used to do).
Reviewed-by: John Johansen <john.johansen@canonical.com>
ACKed-by: John Johansen <john.johansen@canonical.com>
Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
Cc: stable@vger.kernel.org
2011-12-05 21:43:34 +08:00
|
|
|
/* If the path is not connected to the expected root,
|
2010-07-30 05:47:57 +08:00
|
|
|
* check if it is a sysctl and handle specially else remove any
|
|
|
|
* leading / that __d_path may have returned.
|
|
|
|
* Unless
|
|
|
|
* specifically directed to connect the path,
|
|
|
|
* OR
|
|
|
|
* if in a chroot and doing chroot relative paths and the path
|
|
|
|
* resolves to the namespace root (would be connected outside
|
|
|
|
* of chroot) and specifically directed to connect paths to
|
|
|
|
* namespace root.
|
|
|
|
*/
|
|
|
|
if (!connected) {
|
fix apparmor dereferencing potentially freed dentry, sanitize __d_path() API
__d_path() API is asking for trouble and in case of apparmor d_namespace_path()
getting just that. The root cause is that when __d_path() misses the root
it had been told to look for, it stores the location of the most remote ancestor
in *root. Without grabbing references. Sure, at the moment of call it had
been pinned down by what we have in *path. And if we raced with umount -l, we
could have very well stopped at vfsmount/dentry that got freed as soon as
prepend_path() dropped vfsmount_lock.
It is safe to compare these pointers with pre-existing (and known to be still
alive) vfsmount and dentry, as long as all we are asking is "is it the same
address?". Dereferencing is not safe and apparmor ended up stepping into
that. d_namespace_path() really wants to examine the place where we stopped,
even if it's not connected to our namespace. As the result, it looked
at ->d_sb->s_magic of a dentry that might've been already freed by that point.
All other callers had been careful enough to avoid that, but it's really
a bad interface - it invites that kind of trouble.
The fix is fairly straightforward, even though it's bigger than I'd like:
* prepend_path() root argument becomes const.
* __d_path() is never called with NULL/NULL root. It was a kludge
to start with. Instead, we have an explicit function - d_absolute_root().
Same as __d_path(), except that it doesn't get root passed and stops where
it stops. apparmor and tomoyo are using it.
* __d_path() returns NULL on path outside of root. The main
caller is show_mountinfo() and that's precisely what we pass root for - to
skip those outside chroot jail. Those who don't want that can (and do)
use d_path().
* __d_path() root argument becomes const. Everyone agrees, I hope.
* apparmor does *NOT* try to use __d_path() or any of its variants
when it sees that path->mnt is an internal vfsmount. In that case it's
definitely not mounted anywhere and dentry_path() is exactly what we want
there. Handling of sysctl()-triggered weirdness is moved to that place.
* if apparmor is asked to do pathname relative to chroot jail
and __d_path() tells it we it's not in that jail, the sucker just calls
d_absolute_path() instead. That's the other remaining caller of __d_path(),
BTW.
* seq_path_root() does _NOT_ return -ENAMETOOLONG (it's stupid anyway -
the normal seq_file logics will take care of growing the buffer and redoing
the call of ->show() just fine). However, if it gets path not reachable
from root, it returns SEQ_SKIP. The only caller adjusted (i.e. stopped
ignoring the return value as it used to do).
Reviewed-by: John Johansen <john.johansen@canonical.com>
ACKed-by: John Johansen <john.johansen@canonical.com>
Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
Cc: stable@vger.kernel.org
2011-12-05 21:43:34 +08:00
|
|
|
if (!(flags & PATH_CONNECT_PATH) &&
|
2010-07-30 05:47:57 +08:00
|
|
|
!(((flags & CHROOT_NSCONNECT) == CHROOT_NSCONNECT) &&
|
fix apparmor dereferencing potentially freed dentry, sanitize __d_path() API
__d_path() API is asking for trouble and in case of apparmor d_namespace_path()
getting just that. The root cause is that when __d_path() misses the root
it had been told to look for, it stores the location of the most remote ancestor
in *root. Without grabbing references. Sure, at the moment of call it had
been pinned down by what we have in *path. And if we raced with umount -l, we
could have very well stopped at vfsmount/dentry that got freed as soon as
prepend_path() dropped vfsmount_lock.
It is safe to compare these pointers with pre-existing (and known to be still
alive) vfsmount and dentry, as long as all we are asking is "is it the same
address?". Dereferencing is not safe and apparmor ended up stepping into
that. d_namespace_path() really wants to examine the place where we stopped,
even if it's not connected to our namespace. As the result, it looked
at ->d_sb->s_magic of a dentry that might've been already freed by that point.
All other callers had been careful enough to avoid that, but it's really
a bad interface - it invites that kind of trouble.
The fix is fairly straightforward, even though it's bigger than I'd like:
* prepend_path() root argument becomes const.
* __d_path() is never called with NULL/NULL root. It was a kludge
to start with. Instead, we have an explicit function - d_absolute_root().
Same as __d_path(), except that it doesn't get root passed and stops where
it stops. apparmor and tomoyo are using it.
* __d_path() returns NULL on path outside of root. The main
caller is show_mountinfo() and that's precisely what we pass root for - to
skip those outside chroot jail. Those who don't want that can (and do)
use d_path().
* __d_path() root argument becomes const. Everyone agrees, I hope.
* apparmor does *NOT* try to use __d_path() or any of its variants
when it sees that path->mnt is an internal vfsmount. In that case it's
definitely not mounted anywhere and dentry_path() is exactly what we want
there. Handling of sysctl()-triggered weirdness is moved to that place.
* if apparmor is asked to do pathname relative to chroot jail
and __d_path() tells it we it's not in that jail, the sucker just calls
d_absolute_path() instead. That's the other remaining caller of __d_path(),
BTW.
* seq_path_root() does _NOT_ return -ENAMETOOLONG (it's stupid anyway -
the normal seq_file logics will take care of growing the buffer and redoing
the call of ->show() just fine). However, if it gets path not reachable
from root, it returns SEQ_SKIP. The only caller adjusted (i.e. stopped
ignoring the return value as it used to do).
Reviewed-by: John Johansen <john.johansen@canonical.com>
ACKed-by: John Johansen <john.johansen@canonical.com>
Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
Cc: stable@vger.kernel.org
2011-12-05 21:43:34 +08:00
|
|
|
our_mnt(path->mnt))) {
|
2010-07-30 05:47:57 +08:00
|
|
|
/* disconnected path, don't return pathname starting
|
|
|
|
* with '/'
|
|
|
|
*/
|
2012-03-11 03:19:51 +08:00
|
|
|
error = -EACCES;
|
2010-07-30 05:47:57 +08:00
|
|
|
if (*res == '/')
|
|
|
|
*name = res + 1;
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
out:
|
|
|
|
return error;
|
|
|
|
}
|
|
|
|
|
|
|
|
/**
|
|
|
|
* get_name_to_buffer - get the pathname to a buffer ensure dir / is appended
|
|
|
|
* @path: path to get name for (NOT NULL)
|
|
|
|
* @flags: flags controlling path lookup
|
|
|
|
* @buffer: buffer to put name in (NOT NULL)
|
|
|
|
* @size: size of buffer
|
|
|
|
* @name: Returns - contains position of path name in @buffer (NOT NULL)
|
|
|
|
*
|
|
|
|
* Returns: %0 else error on failure
|
|
|
|
*/
|
2016-03-26 02:18:14 +08:00
|
|
|
static int get_name_to_buffer(const struct path *path, int flags, char *buffer,
|
2012-02-16 22:20:33 +08:00
|
|
|
int size, char **name, const char **info)
|
2010-07-30 05:47:57 +08:00
|
|
|
{
|
|
|
|
int adjust = (flags & PATH_IS_DIR) ? 1 : 0;
|
|
|
|
int error = d_namespace_path(path, buffer, size - adjust, name, flags);
|
|
|
|
|
|
|
|
if (!error && (flags & PATH_IS_DIR) && (*name)[1] != '\0')
|
|
|
|
/*
|
|
|
|
* Append "/" to the pathname. The root directory is a special
|
|
|
|
* case; it already ends in slash.
|
|
|
|
*/
|
|
|
|
strcpy(&buffer[size - 2], "/");
|
|
|
|
|
2012-02-16 22:20:33 +08:00
|
|
|
if (info && error) {
|
|
|
|
if (error == -ENOENT)
|
|
|
|
*info = "Failed name lookup - deleted entry";
|
2013-02-19 08:02:34 +08:00
|
|
|
else if (error == -EACCES)
|
2012-02-16 22:20:33 +08:00
|
|
|
*info = "Failed name lookup - disconnected path";
|
|
|
|
else if (error == -ENAMETOOLONG)
|
|
|
|
*info = "Failed name lookup - name too long";
|
|
|
|
else
|
|
|
|
*info = "Failed name lookup";
|
|
|
|
}
|
|
|
|
|
2010-07-30 05:47:57 +08:00
|
|
|
return error;
|
|
|
|
}
|
|
|
|
|
|
|
|
/**
|
2012-02-16 22:20:33 +08:00
|
|
|
* aa_path_name - compute the pathname of a file
|
2010-07-30 05:47:57 +08:00
|
|
|
* @path: path the file (NOT NULL)
|
|
|
|
* @flags: flags controlling path name generation
|
|
|
|
* @buffer: buffer that aa_get_name() allocated (NOT NULL)
|
|
|
|
* @name: Returns - the generated path name if !error (NOT NULL)
|
2012-02-16 22:20:33 +08:00
|
|
|
* @info: Returns - information on why the path lookup failed (MAYBE NULL)
|
2010-07-30 05:47:57 +08:00
|
|
|
*
|
|
|
|
* @name is a pointer to the beginning of the pathname (which usually differs
|
|
|
|
* from the beginning of the buffer), or NULL. If there is an error @name
|
|
|
|
* may contain a partial or invalid name that can be used for audit purposes,
|
|
|
|
* but it can not be used for mediation.
|
|
|
|
*
|
|
|
|
* We need PATH_IS_DIR to indicate whether the file is a directory or not
|
|
|
|
* because the file may not yet exist, and so we cannot check the inode's
|
|
|
|
* file type.
|
|
|
|
*
|
|
|
|
* Returns: %0 else error code if could retrieve name
|
|
|
|
*/
|
2016-03-26 02:18:14 +08:00
|
|
|
int aa_path_name(const struct path *path, int flags, char **buffer,
|
|
|
|
const char **name, const char **info)
|
2010-07-30 05:47:57 +08:00
|
|
|
{
|
|
|
|
char *buf, *str = NULL;
|
|
|
|
int size = 256;
|
|
|
|
int error;
|
|
|
|
|
|
|
|
*name = NULL;
|
|
|
|
*buffer = NULL;
|
|
|
|
for (;;) {
|
|
|
|
/* freed by caller */
|
|
|
|
buf = kmalloc(size, GFP_KERNEL);
|
|
|
|
if (!buf)
|
|
|
|
return -ENOMEM;
|
|
|
|
|
2012-02-16 22:20:33 +08:00
|
|
|
error = get_name_to_buffer(path, flags, buf, size, &str, info);
|
2010-07-30 05:47:57 +08:00
|
|
|
if (error != -ENAMETOOLONG)
|
|
|
|
break;
|
|
|
|
|
|
|
|
kfree(buf);
|
|
|
|
size <<= 1;
|
|
|
|
if (size > aa_g_path_max)
|
|
|
|
return -ENAMETOOLONG;
|
2012-02-16 22:20:33 +08:00
|
|
|
*info = NULL;
|
2010-07-30 05:47:57 +08:00
|
|
|
}
|
|
|
|
*buffer = buf;
|
|
|
|
*name = str;
|
|
|
|
|
|
|
|
return error;
|
|
|
|
}
|