From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753175AbdCIV3b (ORCPT ); Thu, 9 Mar 2017 16:29:31 -0500 Received: from mail-pf0-f174.google.com ([209.85.192.174]:35877 "EHLO mail-pf0-f174.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752466AbdCIV3a (ORCPT ); Thu, 9 Mar 2017 16:29:30 -0500 From: Tycho Andersen To: Kees Cook , James Morris Cc: linux-security-module@vger.kernel.org, linux-kernel@vger.kernel.org, Tycho Andersen , "Serge E. Hallyn" Subject: [PATCH v3] security/Kconfig: further restrict HARDENED_USERCOPY Date: Thu, 9 Mar 2017 13:19:49 -0800 Message-Id: <1489094389-28007-1-git-send-email-tycho@docker.com> X-Mailer: git-send-email 2.7.4 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org It doesn't make sense to have HARDENED_USERCOPY when either /dev/kmem is enabled or /dev/mem can be used to read kernel memory (i.e. !STRICT_DEVMEM). v2: add !MMU depend as well v3: drop !MMU, s/ARCH_HAS_DEVMEM_IS_ALLOWED/DEVMEM, which makes the above commit message actually match the logic again Signed-off-by: Tycho Andersen CC: Kees Cook CC: "Serge E. Hallyn" CC: James Morris --- security/Kconfig | 2 ++ 1 file changed, 2 insertions(+) diff --git a/security/Kconfig b/security/Kconfig index 3ff1bf9..4619cee 100644 --- a/security/Kconfig +++ b/security/Kconfig @@ -142,6 +142,8 @@ config HARDENED_USERCOPY bool "Harden memory copies between kernel and userspace" depends on HAVE_ARCH_HARDENED_USERCOPY depends on HAVE_HARDENED_USERCOPY_ALLOCATOR + depends on !DEVKMEM + depends on !DEVMEM || STRICT_DEVMEM select BUG help This option checks for obviously wrong memory regions when -- 2.7.4