Received: by 2002:ad5:474a:0:0:0:0:0 with SMTP id i10csp9226674imu; Wed, 5 Dec 2018 00:53:38 -0800 (PST) X-Google-Smtp-Source: AFSGD/X7X6+4jTi4WyHlXVnS+Wsk23T+v0bBmAZ1GBrR8lcn/sv4ooh/tidz/gF8djUcdmQEk0e6 X-Received: by 2002:a63:b4c:: with SMTP id a12mr20007033pgl.131.1544000018568; Wed, 05 Dec 2018 00:53:38 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1544000018; cv=none; d=google.com; s=arc-20160816; b=iyhRA7z4NGfz8FZXZsxYUXLWtybyqMcNWCt088wzjJdKtbDHZKpMXXq+22ANiOYl2Y S2udDzeuqCGwzp/WPkJRKZo39vW7KDQmh2J/xaX1Bwmppsi+R7Ja4wJk6pxft8YLAwEF iDXPHkT36bxF56zu42Akw7DETBGsTrR/m/NEiAhfIi+r9btzRQskfx/d0LLVwqrPhkkq H7D21oM1vlm88cXEvdctxdjKxEPP4t82qmTsJhJhYF3/1Dy8Hj+zarzUeTnGyQfATVf1 ZP1dlmJrgQCFXU1EysWAAMfWJoNhZWnrNZn3zoCeM4FXEybCGVWPoG4t/ccNabmTsjZZ V3Ww== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:mime-version:references:in-reply-to :message-id:date:subject:cc:to:from; bh=tnG+D3+P/uhHb4tsnbYU37Tp+I7VX0og8VTMzR6Nd/M=; b=WpAu3x53CzU9th6WsPEno0XzZrw+qGA5HGFsNm0Jt7Mr2iz74ovRhR6BKzNFrr+lNo 9PltAi+3fOvuxj7h/jZkV79ckcQ9bOjk2Xs+DHdW+whBBPIDS92jtcACv/tWDiMDsaYw 99MV80wy+J1QcagbPRXKAQjcWnCIYWFJ5SQmZo/isVY2rXrqKHFi+eBbsEgXmzt2REXl b12omfCPfe98Uws1MfqQ9aou2jd6IbPKlu2q1NYYgq2rfTE5Ogq4FpOBFRMb0oyGnZrQ +/BbwnmX2WM+LEIZbGCF2Zj5gkdSkT8NqcERxx0yHIou2A+5HwYyv+OV7pEe3Y5UWDMn w3nA== ARC-Authentication-Results: i=1; mx.google.com; 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=fail (p=NONE sp=NONE dis=NONE) header.from=vmware.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id q5si18443270pgr.435.2018.12.05.00.53.23; Wed, 05 Dec 2018 00:53:38 -0800 (PST) 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; 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=fail (p=NONE sp=NONE dis=NONE) header.from=vmware.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727557AbeLEIwd (ORCPT + 99 others); Wed, 5 Dec 2018 03:52:33 -0500 Received: from ex13-edg-ou-001.vmware.com ([208.91.0.189]:33316 "EHLO EX13-EDG-OU-001.vmware.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727337AbeLEIwN (ORCPT ); Wed, 5 Dec 2018 03:52:13 -0500 Received: from sc9-mailhost3.vmware.com (10.113.161.73) by EX13-EDG-OU-001.vmware.com (10.113.208.155) with Microsoft SMTP Server id 15.0.1156.6; Wed, 5 Dec 2018 00:52:03 -0800 Received: from sc2-haas01-esx0118.eng.vmware.com (sc2-haas01-esx0118.eng.vmware.com [10.172.44.118]) by sc9-mailhost3.vmware.com (Postfix) with ESMTP id 3EDB341392; Wed, 5 Dec 2018 00:52:05 -0800 (PST) From: Nadav Amit To: Ingo Molnar CC: , , "H. Peter Anvin" , Thomas Gleixner , Borislav Petkov , Andy Lutomirski , Nadav Amit , Dave Hansen , Peter Zijlstra , , , , Nadav Amit , Rick P Edgecombe , Will Deacon Subject: [PATCH v7 13/14] module: Do not set nx for module memory before freeing Date: Tue, 4 Dec 2018 17:34:07 -0800 Message-ID: <20181205013408.47725-14-namit@vmware.com> X-Mailer: git-send-email 2.17.1 In-Reply-To: <20181205013408.47725-1-namit@vmware.com> References: <20181205013408.47725-1-namit@vmware.com> MIME-Version: 1.0 Content-Type: text/plain Received-SPF: None (EX13-EDG-OU-001.vmware.com: namit@vmware.com does not designate permitted sender hosts) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org When module memory is about to be freed, there is no apparent reason to make it (and its data) executable, but that's exactly what is done today. This is not efficient and not secure. There are various theories why it was done, but none of them seem as something that really require it today. nios2 uses kmalloc for module memory, but anyhow it does not change the PTEs of the module memory. In x86, changing vmalloc'd memory mappings also modifies the direct mapping alias, but the NX-bit is not modified in such way. So let's remove it. Andy suggested that the changes of the PTEs can be avoided (excluding the direct-mapping alias), which is true. However, in x86 it requires some cleanup of the contiguous page allocator, which is outside of the scope of this patch-set. Cc: Rick P Edgecombe Cc: Will Deacon Cc: Andy Lutomirski Signed-off-by: Nadav Amit --- kernel/module.c | 35 ++++++++++++++++++++++------------- 1 file changed, 22 insertions(+), 13 deletions(-) diff --git a/kernel/module.c b/kernel/module.c index 7cb207249437..57c5b23746e7 100644 --- a/kernel/module.c +++ b/kernel/module.c @@ -2027,20 +2027,29 @@ void set_all_modules_text_ro(void) mutex_unlock(&module_mutex); } -static void disable_ro_nx(const struct module_layout *layout) +static void module_restore_mappings(const struct module_layout *layout) { - if (rodata_enabled) { - frob_text(layout, set_memory_rw); - frob_rodata(layout, set_memory_rw); - frob_ro_after_init(layout, set_memory_rw); - } - frob_rodata(layout, set_memory_x); - frob_ro_after_init(layout, set_memory_x); - frob_writable_data(layout, set_memory_x); + /* + * First, make the mappings of the code non-executable to prevent + * transient W+X mappings from being set when the text is set as RW. + */ + frob_text(layout, set_memory_nx); + + if (!rodata_enabled) + return; + + /* + * Second, set the memory as writable. Although the module memory is + * about to be freed, these calls are required (at least on x86) to + * restore the direct map to its "correct" state. + */ + frob_text(layout, set_memory_rw); + frob_rodata(layout, set_memory_rw); + frob_ro_after_init(layout, set_memory_rw); } #else -static void disable_ro_nx(const struct module_layout *layout) { } +static void module_restore_mappings(const struct module_layout *layout) { } static void module_enable_nx(const struct module *mod) { } static void module_disable_nx(const struct module *mod) { } #endif @@ -2173,7 +2182,7 @@ static void free_module(struct module *mod) mutex_unlock(&module_mutex); /* This may be empty, but that's OK */ - disable_ro_nx(&mod->init_layout); + module_restore_mappings(&mod->init_layout); module_arch_freeing_init(mod); module_memfree(mod->init_layout.base); kfree(mod->args); @@ -2183,7 +2192,7 @@ static void free_module(struct module *mod) lockdep_free_key_range(mod->core_layout.base, mod->core_layout.size); /* Finally, free the core (containing the module structure) */ - disable_ro_nx(&mod->core_layout); + module_restore_mappings(&mod->core_layout); module_memfree(mod->core_layout.base); } @@ -3507,7 +3516,7 @@ static noinline int do_init_module(struct module *mod) #endif module_enable_ro(mod, true); mod_tree_remove_init(mod); - disable_ro_nx(&mod->init_layout); + module_restore_mappings(&mod->init_layout); module_arch_freeing_init(mod); mod->init_layout.base = NULL; mod->init_layout.size = 0; -- 2.17.1