Received: by 2002:a05:6a10:16a7:0:0:0:0 with SMTP id gp39csp806835pxb; Thu, 5 Nov 2020 13:35:14 -0800 (PST) X-Google-Smtp-Source: ABdhPJy0FlE91VqrgToE7/lxiB1DbpyKnx39IsxFyRlitgIxRIXRU3Q5DMmv5Z7qAb/d0oDunLFz X-Received: by 2002:a17:906:c186:: with SMTP id g6mr4097996ejz.465.1604612113895; Thu, 05 Nov 2020 13:35:13 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1604612113; cv=none; d=google.com; s=arc-20160816; b=BkC3rduJ9z/UN9dYjlBsEVUjKCb3nbzdKkE+nemdTpUZkZ+KhkYr4IF2Ix+Wrz80yV RMiiMs1jZ0XF9sRrRE3X9LaRnQvOK7Q2uDrAjuQ8hsUbdiv9jbCGqslafNozKPXySGtq a2elB0+cymSSqX/+I2StAPnczruw6tkSxWdimGlBKZ6HdOa/WoatF5qFRXF3yv1t5Z8Z YbhuD+O48vtAjrs8LeaQtEbXQvXMIqKba5v6BKq0aBHUgAYK2+nvuPu43dfdgP9f9Ho8 EZiOL1e2/uDFrHTKVq8p7M3S/FIMQuI4oxESN8UMeWFzhfOYURDiFKMQxkq51umkUSuR WvPA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:cc:to:from:subject:mime-version:message-id:date :sender:dkim-signature; bh=UJkZX1H27CEJgxyCZBCEdyDuRuG5xM7XtCA2iT1WI+8=; b=YEUGcrpES0S9dyC363idL/krFaO2s6EFouT9W/L+lPxnx2858xxB4Qb/l47JfS4mib hnaj89daKQ4F4x+x/FaC90opcDCIP3lw5ohfUmNVLvkuM2qEXUjqouTI0B7J7oOolAHx DMN20+YDDQMbR7tNH/Mc4eC0EkHsblfWcNm849uU/UmVJgnB8N/577WQ4hS/ufH160wC T+ywLzNUEE7oZXcBUXghzdbIgGR6YUmDxt6vgDo05RNnG0IOpp1xY4cHhd46sZsUwJTc ukNJ8H3pyEMEhQfH3j41OnpovIPkz9sNh+XDFIP6YDf7FEujwXbHDkVjTOfqkyX5h+dU RXzA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@google.com header.s=20161025 header.b=cGpcfBV4; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=REJECT sp=REJECT dis=NONE) header.from=google.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id k26si1991463ejz.41.2020.11.05.13.34.50; Thu, 05 Nov 2020 13:35:13 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@google.com header.s=20161025 header.b=cGpcfBV4; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=REJECT sp=REJECT dis=NONE) header.from=google.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1732265AbgKEVd3 (ORCPT + 99 others); Thu, 5 Nov 2020 16:33:29 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:54630 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1732192AbgKEVd2 (ORCPT ); Thu, 5 Nov 2020 16:33:28 -0500 Received: from mail-qk1-x749.google.com (mail-qk1-x749.google.com [IPv6:2607:f8b0:4864:20::749]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 68765C0613D2 for ; Thu, 5 Nov 2020 13:33:28 -0800 (PST) Received: by mail-qk1-x749.google.com with SMTP id i8so1913320qka.15 for ; Thu, 05 Nov 2020 13:33:28 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=sender:date:message-id:mime-version:subject:from:to:cc; bh=UJkZX1H27CEJgxyCZBCEdyDuRuG5xM7XtCA2iT1WI+8=; b=cGpcfBV4YiQi3w9EyBV0GNDbdFcCrKpU41+zMIR0Wy6uDFL2N31r1Re2FRryvxqlGL jN+9wlEOoBhIuGUsPgJmcuo+wITHwciNSfVqaozV/ozE/Roe3wSKl0g+SkC4sRDpgCmz cD6W9dnpWpoC+tNGfGi/a0++8RRMR7CbjiauSkhFxW0gJp+I/PA2MoOun6XV5+PrWHjo rCwNjfCBvtCMsgFDq1iUmJ3OcsYWesmSMYMw623eJHlqVHiFXvQDAryixpZ3ZlHTyT52 ncFuO4ZHDPAPpmTRoLlAz4Vi875h8In42QAinh53SOLoAmv6ENU6PRi68sk/F0LwUdch t3vA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:sender:date:message-id:mime-version:subject:from :to:cc; bh=UJkZX1H27CEJgxyCZBCEdyDuRuG5xM7XtCA2iT1WI+8=; b=G8p4XbbKnCkoQNCP4r59H2AujSjVxNnM0dEbZIucZl9K15KmLVqLc3by29mRMDmqJF CIV++FU/oC2G8ZDbnCYpmgYc62Bzo5+NN0wWT0J+o6bGYz3JvAiWLoXzK3Pvw6rhKqad LbCcAc5f39nvj4WAgjNTwXvF9jKefCy3jdTseGcffN6WBjXCnEFwdyBte/1IV9dyiaC2 HBnJc7LvEcAcMi3ePaCJQB94rfRMVwzBXRqdqpVs5qioxB1e2UNhNxkdNFiUhEUM/dVL gTc5/LAd2JAB99XNvYn2y+0PUAFPinKRkabjELbRPfNd9J4OtxjuPAIoIdc0r8fWTlvU qapw== X-Gm-Message-State: AOAM532ZxYORi+2DwHRlNHSQpLj5KVeQop/+0p8nIyml9kct0KFpZNn+ 7B9uWm0OyWBYPD/LdnKLiGnxJD6LjYe/Mk/vAg== Sender: "lokeshgidra via sendgmr" X-Received: from lg.mtv.corp.google.com ([2620:15c:211:202:f693:9fff:fef4:29dd]) (user=lokeshgidra job=sendgmr) by 2002:a0c:b44a:: with SMTP id e10mr4421795qvf.4.1604612007309; Thu, 05 Nov 2020 13:33:27 -0800 (PST) Date: Thu, 5 Nov 2020 13:33:20 -0800 Message-Id: <20201105213324.3111570-1-lokeshgidra@google.com> Mime-Version: 1.0 X-Mailer: git-send-email 2.29.1.341.ge80a0c044ae-goog Subject: [PATCH v11 0/4] SELinux support for anonymous inodes and UFFD From: Lokesh Gidra To: Andrea Arcangeli , Alexander Viro , James Morris , Stephen Smalley , Casey Schaufler , Eric Biggers Cc: "Serge E. Hallyn" , Paul Moore , Eric Paris , Lokesh Gidra , Daniel Colascione , Kees Cook , "Eric W. Biederman" , KP Singh , David Howells , Thomas Cedeno , Anders Roxell , Sami Tolvanen , Matthew Garrett , Aaron Goidel , Randy Dunlap , "Joel Fernandes (Google)" , YueHaibing , Christian Brauner , Alexei Starovoitov , Alexey Budankov , Adrian Reber , Aleksa Sarai , linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org, linux-security-module@vger.kernel.org, selinux@vger.kernel.org, kaleshsingh@google.com, calin@google.com, surenb@google.com, nnk@google.com, jeffv@google.com, kernel-team@android.com, linux-mm@kvack.org, Andrew Morton , hch@infradead.org Content-Type: text/plain; charset="UTF-8" Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Userfaultfd in unprivileged contexts could be potentially very useful. We'd like to harden userfaultfd to make such unprivileged use less risky. This patch series allows SELinux to manage userfaultfd file descriptors and in the future, other kinds of anonymous-inode-based file descriptor. SELinux policy authors can apply policy types to anonymous inodes by providing name-based transition rules keyed off the anonymous inode internal name ( "[userfaultfd]" in the case of userfaultfd(2) file descriptors) and applying policy to the new SIDs thus produced. With SELinux managed userfaultfd, an admin can control creation and movement of the file descriptors. In particular, handling of a userfaultfd descriptor by a different process is essentially a ptrace access into the process, without any of the corresponding security_ptrace_access_check() checks. For privacy, the admin may want to deny such accesses, which is possible with SELinux support. Inside the kernel, a new anon_inode interface, anon_inode_getfd_secure, allows callers to opt into this SELinux management. In this new "secure" mode, anon_inodes create new ephemeral inodes for anonymous file objects instead of reusing the normal anon_inodes singleton dummy inode. A new LSM hook gives security modules an opportunity to configure and veto these ephemeral inodes. This patch series is one of two fork of [1] and is an alternative to [2]. The primary difference between the two patch series is that this partch series creates a unique inode for each "secure" anonymous inode, while the other patch series ([2]) continues using the singleton dummy anonymous inode and adds a way to attach SELinux security information directly to file objects. I prefer the approach in this patch series because 1) it's a smaller patch than [2], and 2) it produces a more regular security architecture: in this patch series, secure anonymous inodes aren't S_PRIVATE and they maintain the SELinux property that the label for a file is in its inode. We do need an additional inode per anonymous file, but per-struct-file inode creation doesn't seem to be a problem for pipes and sockets. The previous version of this feature ([1]) created a new SELinux security class for userfaultfd file descriptors. This version adopts the generic transition-based approach of [2]. This patch series also differs from [2] in that it doesn't affect all anonymous inodes right away --- instead requiring anon_inodes callers to opt in --- but this difference isn't one of basic approach. The important question to resolve is whether we should be creating new inodes or enhancing per-file data. Changes from the first version of the patch: - Removed some error checks - Defined a new anon_inode SELinux class to resolve the ambiguity in [3] - Inherit sclass as well as descriptor from context inode Changes from the second version of the patch: - Fixed example policy in the commit message to reflect the use of the new anon_inode class. Changes from the third version of the patch: - Dropped the fops parameter to the LSM hook - Documented hook parameters - Fixed incorrect class used for SELinux transition - Removed stray UFFD changed early in the series - Removed a redundant ERR_PTR(PTR_ERR()) Changes from the fourth version of the patch: - Removed an unused parameter from an internal function - Fixed function documentation Changes from the fifth version of the patch: - Fixed function documentation in fs/anon_inodes.c and include/linux/lsm_hooks.h - Used anon_inode_getfd_secure() in userfaultfd() syscall and removed owner from userfaultfd_ctx. Changes from the sixth version of the patch: - Removed definition of anon_inode_getfile_secure() as there are no callers. - Simplified function description of anon_inode_getfd_secure(). - Elaborated more on the purpose of 'context_inode' in commit message. Changes from the seventh version of the patch: - Fixed error handling in _anon_inode_getfile(). - Fixed minor comment and indentation related issues. Changes from the eighth version of the patch: - Replaced selinux_state.initialized with selinux_state.initialized Changes from the ninth version of the patch: - Fixed function names in fs/anon_inodes.c - Fixed comment of anon_inode_getfd_secure() - Fixed name of the patch wherein userfaultfd code uses anon_inode_getfd_secure() Changes from the tenth version of the patch: - Split first patch into VFS and LSM specific patches - Fixed comments in fs/anon_inodes.c - Fixed comment of alloc_anon_inode() [1] https://lore.kernel.org/lkml/20200211225547.235083-1-dancol@google.com/ [2] https://lore.kernel.org/linux-fsdevel/20200213194157.5877-1-sds@tycho.nsa.gov/ [3] https://lore.kernel.org/lkml/23f725ca-5b5a-5938-fcc8-5bbbfc9ba9bc@tycho.nsa.gov/ Daniel Colascione (3): fs: add LSM-supporting anon-inode interface selinux: teach SELinux about anonymous inodes userfaultfd: use secure anon inodes for userfaultfd Lokesh Gidra (1): security: add inode_init_security_anon() LSM hook fs/anon_inodes.c | 149 ++++++++++++++++++++-------- fs/libfs.c | 6 +- fs/userfaultfd.c | 19 ++-- include/linux/anon_inodes.h | 5 + include/linux/lsm_hook_defs.h | 2 + include/linux/lsm_hooks.h | 9 ++ include/linux/security.h | 10 ++ security/security.c | 8 ++ security/selinux/hooks.c | 53 ++++++++++ security/selinux/include/classmap.h | 2 + 10 files changed, 211 insertions(+), 52 deletions(-) -- 2.29.1.341.ge80a0c044ae-goog