Received: by 2002:a25:8b12:0:0:0:0:0 with SMTP id i18csp3355354ybl; Mon, 19 Aug 2019 17:22:21 -0700 (PDT) X-Google-Smtp-Source: APXvYqxq+FvT01QpIcUYUEyK2cg3JjUD6iW7uP0k4Uq5+z0KfP55BVGEwmo6Ju9PuJWmRb/wcyPt X-Received: by 2002:a17:902:524:: with SMTP id 33mr25721681plf.27.1566260541573; Mon, 19 Aug 2019 17:22:21 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1566260541; cv=none; d=google.com; s=arc-20160816; b=TaqKxUXYkfZk7XKYl4cCSRToCo+LyCloXbWAakPZ6A3BWLapkWGMp2ZsOTO4EVAhGj 8nZJ2L00dGK5TEELOcNXw6OJAWAEjdASXLURwr4BNBOQiE51/l79IokYJ81KZkDkjSBJ R7lYue/2AvtlnblsJm/YsLAunOIFyQoE1WzVOOg4aWdfHDkH4Psdn7gh6Eq9nrUfEhct Ef7P56D33K4wq4qKgOmjR+SxvcTF9naa8w7834y570Yt+LE+ik5lv3A5nfRZ9ImEojbR 8CFQLuDqb7hT8xiChd9pwYLJWhsl4mshlMEXCtECPcbZB7lClSFnQE30SfIOlDd68nSv 8GBg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:cc:to:from:subject:references :mime-version:message-id:in-reply-to:date:dkim-signature; bh=010QS9WoWtGoiC1ndkOQ/THJSGP3hTPvp7YVgOrBMsw=; b=0IGqPsMYE8TLTgP1jOApQREegm5D9yvoJ4Qlf9i4/E0ixgLWNXYWtkYSOKkmeknVW/ dVND8STWRdHppUSCCGJmeOh+HlvfBOpnzUNLs1N2TBgxDV1+ESOuNKJPGWkgypbBJtNT Zh35p6qdf/aFOlL1lGw0KKPQCG6BB2wB3wYVcCsuC4Jgylckx5gqZQ6LYi0tFVjuDrGC 9nJAVbFFi4Ww6W2thYacDgOrY8NwWIyXLVHKm2mum5Bjhnh2CEyvadsBeslSuxOyJwug dZ6IVvgLQNuShRe/EGMf0s5VwIJphH9+XVph6H4W0g5Kofc+cV+K25LrVivsmbM5twH8 u5sA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@google.com header.s=20161025 header.b="S/h/Sfns"; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 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. [209.132.180.67]) by mx.google.com with ESMTP id k33si10784521pgi.563.2019.08.19.17.22.06; Mon, 19 Aug 2019 17:22:21 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@google.com header.s=20161025 header.b="S/h/Sfns"; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 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 S1728920AbfHTASX (ORCPT + 99 others); Mon, 19 Aug 2019 20:18:23 -0400 Received: from mail-vk1-f201.google.com ([209.85.221.201]:42856 "EHLO mail-vk1-f201.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1728883AbfHTASW (ORCPT ); Mon, 19 Aug 2019 20:18:22 -0400 Received: by mail-vk1-f201.google.com with SMTP id t205so2368199vke.9 for ; Mon, 19 Aug 2019 17:18:21 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=date:in-reply-to:message-id:mime-version:references:subject:from:to :cc; bh=010QS9WoWtGoiC1ndkOQ/THJSGP3hTPvp7YVgOrBMsw=; b=S/h/SfnsgFfAPrl/AMQC0M7+bE6qZ2UhyS+NlB+ZHqJgnkxWzZCNeJz6TfFSHpI3b/ WNN4+TiYxCgDaDddsL95FRicBBIij+z1M9yenWIJ4HjBjTBspEIFA2vPk0Sz0ipY84t1 IlhTIsS429DAEC2qUVfOBOokIi/VJjAeeiiADtx2DDSt8luPO7dOH+jf9NwRpCG3BtFv eEmzOiqiMwwe9DpMtd7xo4xxUaPKi76MJqJqb5M4WQuRh5Hli/DB6P9BQgN8trWC1gL7 j4U7P2Yxxv9Ee3ddEPp/VQV1voaUNznzhDu3qaLAzTLpiVxRdQCI2vL/owBk6K3uOtCX wFIw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:in-reply-to:message-id:mime-version :references:subject:from:to:cc; bh=010QS9WoWtGoiC1ndkOQ/THJSGP3hTPvp7YVgOrBMsw=; b=IimgJRVrzpzx3ts710mPKKJTk44VzKBFcIVkqCvYXkOkcmbLjeClZs2w2c4C7Qi5yA ePCXF/cMbj2sSbRO1/ZlhF+5hMKy92pbcTdaidv9jnRInbRl4nXCqL4/YEShj1a2e+r8 ejJIekb0a7ADVSWrYkYnow/GWbaGgLW1TfpuaKd+jV+rRqIejZ3c3qbgbxeSAMDKnUeC nffa88jm/5HLT8nqzVV3xY8Xiwhb8yFWvVsCnVYDDOKaHiON8ZrXq82KHfxMCKHj4X1P vWwt5bLDdT87eBlEl72CmJsWs1wqQp1ZqxFvNO8ccgDatpok+1YOnFPw6vQxMWwwoA01 l85w== X-Gm-Message-State: APjAAAW+Uxhvqrf0bKq1V4HL6Lh32D9NMxmkTRJ+Oxb66L5FLBC8GhUj vKvzk8H5rbwxHjlCjH0U35EZO9tVpgwOZUhUk4P3sQ== X-Received: by 2002:a1f:ec41:: with SMTP id k62mr9132584vkh.32.1566260300517; Mon, 19 Aug 2019 17:18:20 -0700 (PDT) Date: Mon, 19 Aug 2019 17:17:40 -0700 In-Reply-To: <20190820001805.241928-1-matthewgarrett@google.com> Message-Id: <20190820001805.241928-5-matthewgarrett@google.com> Mime-Version: 1.0 References: <20190820001805.241928-1-matthewgarrett@google.com> X-Mailer: git-send-email 2.23.0.rc1.153.gdeed80330f-goog Subject: [PATCH V40 04/29] lockdown: Enforce module signatures if the kernel is locked down From: Matthew Garrett To: jmorris@namei.org Cc: linux-security-module@vger.kernel.org, linux-kernel@vger.kernel.org, linux-api@vger.kernel.org, David Howells , Matthew Garrett , Kees Cook , Jessica Yu Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org From: David Howells If the kernel is locked down, require that all modules have valid signatures that we can verify. I have adjusted the errors generated: (1) If there's no signature (ENODATA) or we can't check it (ENOPKG, ENOKEY), then: (a) If signatures are enforced then EKEYREJECTED is returned. (b) If there's no signature or we can't check it, but the kernel is locked down then EPERM is returned (this is then consistent with other lockdown cases). (2) If the signature is unparseable (EBADMSG, EINVAL), the signature fails the check (EKEYREJECTED) or a system error occurs (eg. ENOMEM), we return the error we got. Note that the X.509 code doesn't check for key expiry as the RTC might not be valid or might not have been transferred to the kernel's clock yet. [Modified by Matthew Garrett to remove the IMA integration. This will be replaced with integration with the IMA architecture policy patchset.] Signed-off-by: David Howells Signed-off-by: Matthew Garrett Reviewed-by: Kees Cook Cc: Jessica Yu Signed-off-by: James Morris --- include/linux/security.h | 1 + init/Kconfig | 5 +++++ kernel/module.c | 37 +++++++++++++++++++++++++++++------- security/lockdown/Kconfig | 1 + security/lockdown/lockdown.c | 1 + 5 files changed, 38 insertions(+), 7 deletions(-) diff --git a/include/linux/security.h b/include/linux/security.h index 74787335d9ce..9e8abb60a99f 100644 --- a/include/linux/security.h +++ b/include/linux/security.h @@ -103,6 +103,7 @@ enum lsm_event { */ enum lockdown_reason { LOCKDOWN_NONE, + LOCKDOWN_MODULE_SIGNATURE, LOCKDOWN_INTEGRITY_MAX, LOCKDOWN_CONFIDENTIALITY_MAX, }; diff --git a/init/Kconfig b/init/Kconfig index 0e2344389501..e6069368f278 100644 --- a/init/Kconfig +++ b/init/Kconfig @@ -1939,6 +1939,11 @@ config MODULE_SIG kernel build dependency so that the signing tool can use its crypto library. + You should enable this option if you wish to use either + CONFIG_SECURITY_LOCKDOWN_LSM or lockdown functionality imposed via + another LSM - otherwise unsigned modules will be loadable regardless + of the lockdown policy. + !!!WARNING!!! If you enable this option, you MUST make sure that the module DOES NOT get stripped after being signed. This includes the debuginfo strip done by some packagers (such as rpmbuild) and diff --git a/kernel/module.c b/kernel/module.c index 80c7c09584cf..2206c08a5e10 100644 --- a/kernel/module.c +++ b/kernel/module.c @@ -2753,8 +2753,9 @@ static inline void kmemleak_load_module(const struct module *mod, #ifdef CONFIG_MODULE_SIG static int module_sig_check(struct load_info *info, int flags) { - int err = -ENOKEY; + int err = -ENODATA; const unsigned long markerlen = sizeof(MODULE_SIG_STRING) - 1; + const char *reason; const void *mod = info->hdr; /* @@ -2769,16 +2770,38 @@ static int module_sig_check(struct load_info *info, int flags) err = mod_verify_sig(mod, info); } - if (!err) { + switch (err) { + case 0: info->sig_ok = true; return 0; - } - /* Not having a signature is only an error if we're strict. */ - if (err == -ENOKEY && !is_module_sig_enforced()) - err = 0; + /* We don't permit modules to be loaded into trusted kernels + * without a valid signature on them, but if we're not + * enforcing, certain errors are non-fatal. + */ + case -ENODATA: + reason = "Loading of unsigned module"; + goto decide; + case -ENOPKG: + reason = "Loading of module with unsupported crypto"; + goto decide; + case -ENOKEY: + reason = "Loading of module with unavailable key"; + decide: + if (is_module_sig_enforced()) { + pr_notice("%s is rejected\n", reason); + return -EKEYREJECTED; + } - return err; + return security_locked_down(LOCKDOWN_MODULE_SIGNATURE); + + /* All other errors are fatal, including nomem, unparseable + * signatures and signature check failures - even if signatures + * aren't required. + */ + default: + return err; + } } #else /* !CONFIG_MODULE_SIG */ static int module_sig_check(struct load_info *info, int flags) diff --git a/security/lockdown/Kconfig b/security/lockdown/Kconfig index 7a1d213227a4..e84ddf484010 100644 --- a/security/lockdown/Kconfig +++ b/security/lockdown/Kconfig @@ -1,6 +1,7 @@ config SECURITY_LOCKDOWN_LSM bool "Basic module for enforcing kernel lockdown" depends on SECURITY + select MODULE_SIG if MODULES help Build support for an LSM that enforces a coarse kernel lockdown behaviour. diff --git a/security/lockdown/lockdown.c b/security/lockdown/lockdown.c index 7172ad75496b..d8e42125a5dd 100644 --- a/security/lockdown/lockdown.c +++ b/security/lockdown/lockdown.c @@ -18,6 +18,7 @@ static enum lockdown_reason kernel_locked_down; static char *lockdown_reasons[LOCKDOWN_CONFIDENTIALITY_MAX+1] = { [LOCKDOWN_NONE] = "none", + [LOCKDOWN_MODULE_SIGNATURE] = "unsigned module loading", [LOCKDOWN_INTEGRITY_MAX] = "integrity", [LOCKDOWN_CONFIDENTIALITY_MAX] = "confidentiality", }; -- 2.23.0.rc1.153.gdeed80330f-goog