public inbox for linux-unionfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Mark Salyzyn <salyzyn@android.com>
To: linux-kernel@vger.kernel.org
Cc: kernel-team@android.com, Mark Salyzyn <salyzyn@android.com>,
	Miklos Szeredi <miklos@szeredi.hu>,
	Jonathan Corbet <corbet@lwn.net>, Vivek Goyal <vgoyal@redhat.com>,
	"Eric W . Biederman" <ebiederm@xmission.com>,
	Amir Goldstein <amir73il@gmail.com>,
	Randy Dunlap <rdunlap@infradead.org>,
	Stephen Smalley <sds@tycho.nsa.gov>,
	linux-unionfs@vger.kernel.org, linux-doc@vger.kernel.org
Subject: [PATCH v14 0/5] overlayfs override_creds=off & nested get xattr fix
Date: Tue, 22 Oct 2019 13:44:45 -0700	[thread overview]
Message-ID: <20191022204453.97058-1-salyzyn@android.com> (raw)

Patch series:

Mark Salyzyn (5):
  Add flags option to get xattr method paired to __vfs_getxattr
  overlayfs: check CAP_DAC_READ_SEARCH before issuing exportfs_decode_fh
  overlayfs: handle XATTR_NOSECURITY flag for get xattr method
  overlayfs: internal getxattr operations without sepolicy checking
  overlayfs: override_creds=off option bypass creator_cred

The first four patches address fundamental security issues that should
be solved regardless of the override_creds=off feature.

The fifth adds the feature depends on these other fixes.

By default, all access to the upper, lower and work directories is the
recorded mounter's MAC and DAC credentials.  The incoming accesses are
checked against the caller's credentials.

If the principles of least privilege are applied for sepolicy, the
mounter's credentials might not overlap the credentials of the caller's
when accessing the overlayfs filesystem.  For example, a file that a
lower DAC privileged caller can execute, is MAC denied to the
generally higher DAC privileged mounter, to prevent an attack vector.

We add the option to turn off override_creds in the mount options; all
subsequent operations after mount on the filesystem will be only the
caller's credentials.  The module boolean parameter and mount option
override_creds is also added as a presence check for this "feature",
existence of /sys/module/overlay/parameters/overlay_creds

Signed-off-by: Mark Salyzyn <salyzyn@android.com>
Cc: Miklos Szeredi <miklos@szeredi.hu>
Cc: Jonathan Corbet <corbet@lwn.net>
Cc: Vivek Goyal <vgoyal@redhat.com>
Cc: Eric W. Biederman <ebiederm@xmission.com>
Cc: Amir Goldstein <amir73il@gmail.com>
Cc: Randy Dunlap <rdunlap@infradead.org>
Cc: Stephen Smalley <sds@tycho.nsa.gov>
Cc: linux-unionfs@vger.kernel.org
Cc: linux-doc@vger.kernel.org
Cc: linux-kernel@vger.kernel.org

---
v14:
- Rejoin, rebase and a few adjustments.

v13:
- Pull out first patch and try to get it in alone feedback, some
  Acks, and then <crickets> because people forgot why we were doing i.

v12:
- Restore squished out patch 2 and 3 in the series,
  then change algorithm to add flags argument.
  Per-thread flag is a large security surface.

v11:
- Squish out v10 introduced patch 2 and 3 in the series,
  then and use per-thread flag instead for nesting.
- Switch name to ovl_do_vds_getxattr for __vds_getxattr wrapper.
- Add sb argument to ovl_revert_creds to match future work.

v10:
- Return NULL on CAP_DAC_READ_SEARCH
- Add __get xattr method to solve sepolicy logging issue
- Drop unnecessary sys_admin sepolicy checking for administrative
  driver internal xattr functions.

v6:
- Drop CONFIG_OVERLAY_FS_OVERRIDE_CREDS.
- Do better with the documentation, drop rationalizations.
- pr_warn message adjusted to report consequences.

v5:
- beefed up the caveats in the Documentation
- Is dependent on
  "overlayfs: check CAP_DAC_READ_SEARCH before issuing exportfs_decode_fh"
  "overlayfs: check CAP_MKNOD before issuing vfs_whiteout"
- Added prwarn when override_creds=off

v4:
- spelling and grammar errors in text

v3:
- Change name from caller_credentials / creator_credentials to the
  boolean override_creds.
- Changed from creator to mounter credentials.
- Updated and fortified the documentation.
- Added CONFIG_OVERLAY_FS_OVERRIDE_CREDS

v2:
- Forward port changed attr to stat, resulting in a build error.
- altered commit message.


 Documentation/filesystems/locking.rst   |  10 +--
 Documentation/filesystems/overlayfs.txt |  23 +++++
 fs/9p/acl.c                             |  51 ++++++-----
 fs/9p/xattr.c                           |  19 ++--
 fs/afs/xattr.c                          | 112 +++++++++++-------------
 fs/btrfs/xattr.c                        |  36 ++++----
 fs/ceph/xattr.c                         |  17 ++--
 fs/cifs/xattr.c                         |  72 +++++++--------
 fs/ecryptfs/crypto.c                    |  20 +++--
 fs/ecryptfs/inode.c                     |  36 +++++---
 fs/ecryptfs/mmap.c                      |  39 +++++----
 fs/erofs/xattr.c                        |   8 +-
 fs/ext2/xattr_security.c                |  16 ++--
 fs/ext2/xattr_trusted.c                 |  15 ++--
 fs/ext2/xattr_user.c                    |  19 ++--
 fs/ext4/xattr_security.c                |  15 ++--
 fs/ext4/xattr_trusted.c                 |  15 ++--
 fs/ext4/xattr_user.c                    |  19 ++--
 fs/f2fs/xattr.c                         |  42 ++++-----
 fs/fuse/xattr.c                         |  23 ++---
 fs/gfs2/xattr.c                         |  18 ++--
 fs/hfs/attr.c                           |  15 ++--
 fs/hfsplus/xattr.c                      |  17 ++--
 fs/hfsplus/xattr_security.c             |  13 ++-
 fs/hfsplus/xattr_trusted.c              |  13 ++-
 fs/hfsplus/xattr_user.c                 |  13 ++-
 fs/jffs2/security.c                     |  16 ++--
 fs/jffs2/xattr_trusted.c                |  16 ++--
 fs/jffs2/xattr_user.c                   |  16 ++--
 fs/jfs/xattr.c                          |  33 ++++---
 fs/kernfs/inode.c                       |  23 +++--
 fs/nfs/nfs4proc.c                       |  28 +++---
 fs/ocfs2/xattr.c                        |  52 +++++------
 fs/orangefs/xattr.c                     |  19 ++--
 fs/overlayfs/copy_up.c                  |   2 +-
 fs/overlayfs/dir.c                      |  17 ++--
 fs/overlayfs/file.c                     |  20 ++---
 fs/overlayfs/inode.c                    |  66 +++++++-------
 fs/overlayfs/namei.c                    |  21 +++--
 fs/overlayfs/overlayfs.h                |   9 +-
 fs/overlayfs/ovl_entry.h                |   1 +
 fs/overlayfs/readdir.c                  |   4 +-
 fs/overlayfs/super.c                    |  75 +++++++++-------
 fs/overlayfs/util.c                     |  44 +++++++---
 fs/posix_acl.c                          |  23 +++--
 fs/reiserfs/xattr.c                     |   2 +-
 fs/reiserfs/xattr_security.c            |  22 +++--
 fs/reiserfs/xattr_trusted.c             |  22 +++--
 fs/reiserfs/xattr_user.c                |  22 +++--
 fs/squashfs/xattr.c                     |  10 +--
 fs/ubifs/xattr.c                        |  33 ++++---
 fs/xattr.c                              | 112 +++++++++++++++---------
 fs/xfs/libxfs/xfs_attr.c                |   4 +-
 fs/xfs/libxfs/xfs_attr.h                |   2 +-
 fs/xfs/xfs_xattr.c                      |  35 ++++----
 include/linux/xattr.h                   |  26 ++++--
 include/uapi/linux/xattr.h              |   7 +-
 mm/shmem.c                              |  21 +++--
 net/socket.c                            |  16 ++--
 security/commoncap.c                    |  29 ++++--
 security/integrity/evm/evm_main.c       |  13 ++-
 security/selinux/hooks.c                |  28 ++++--
 security/smack/smack_lsm.c              |  38 +++++---
 63 files changed, 852 insertions(+), 771 deletions(-)

-- 
2.23.0.866.gb869b98d4c-goog

             reply	other threads:[~2019-10-22 20:44 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-22 20:44 Mark Salyzyn [this message]
2019-10-22 20:44 ` [PATCH v14 1/5] Add flags option to get xattr method paired to __vfs_getxattr Mark Salyzyn
2019-10-22 22:13   ` Andreas Dilger
2019-10-24  4:57     ` Amir Goldstein
2019-11-04 21:51       ` Mark Salyzyn
2019-10-25  4:39   ` e984eb5108: BUG:kernel_NULL_pointer_dereference,address kernel test robot
2019-10-22 20:44 ` [PATCH v14 2/5] overlayfs: check CAP_DAC_READ_SEARCH before issuing exportfs_decode_fh Mark Salyzyn
2019-10-23  6:17   ` Amir Goldstein
2019-10-23  8:08   ` Miklos Szeredi
2019-10-27  7:24     ` Amir Goldstein
2019-10-28 16:27       ` J. Bruce Fields
2019-10-22 20:44 ` [PATCH v14 3/5] overlayfs: handle XATTR_NOSECURITY flag for get xattr method Mark Salyzyn
2019-10-22 20:44 ` [PATCH v14 4/5] overlayfs: internal getxattr operations without sepolicy checking Mark Salyzyn
2019-10-23  6:39   ` Amir Goldstein
2019-11-04 21:47     ` Mark Salyzyn
2019-10-22 20:44 ` [PATCH v14 5/5] overlayfs: override_creds=off option bypass creator_cred Mark Salyzyn
2019-10-23  6:54 ` [PATCH v14 0/5] overlayfs override_creds=off & nested get xattr fix Amir Goldstein
2019-10-23 14:13   ` Mark Salyzyn
2019-10-24  5:28     ` Amir Goldstein

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=20191022204453.97058-1-salyzyn@android.com \
    --to=salyzyn@android.com \
    --cc=amir73il@gmail.com \
    --cc=corbet@lwn.net \
    --cc=ebiederm@xmission.com \
    --cc=kernel-team@android.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-unionfs@vger.kernel.org \
    --cc=miklos@szeredi.hu \
    --cc=rdunlap@infradead.org \
    --cc=sds@tycho.nsa.gov \
    --cc=vgoyal@redhat.com \
    /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