Received: by 2002:a05:6358:d09b:b0:dc:cd0c:909e with SMTP id jc27csp2952055rwb; Fri, 9 Dec 2022 08:12:42 -0800 (PST) X-Google-Smtp-Source: AA0mqf69KXKTUXs1KuPdsY068sSiPESD6nuw5iUnDeTUJQ92m7larNJ/NwPNq4UO6ARzYst2ztfN X-Received: by 2002:a05:6a00:26c5:b0:576:fb7c:7aa3 with SMTP id p5-20020a056a0026c500b00576fb7c7aa3mr5946087pfw.14.1670602362493; Fri, 09 Dec 2022 08:12:42 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1670602362; cv=none; d=google.com; s=arc-20160816; b=eGkWrM2RldB4WzADcPNHYf6QrTBHiHhxJYu690TSdIlOhIBX37b2eY1ow1Jy5JtOU8 Nq/VvUtYgCtvGHRDpEIa3ZDhAewc0JpkUWGDsERrPnSH+IuUT85UI25zSTmJfBNNJtwk hVQbJlBXfTi3TnAgVfvjHuakE7JTJUWD0fGeG0DUYKUTN4+27kuZ+nUq5TAfvegfv50Z jI38lsAxDrMKyjjzA1RSsGZlhNfbkKD10dCUSGaQjQipmDvCQhBnAoX13YiYpgPlEAyV 5TDmf/iwgRNwy0EGEMquRaWeAuQbKHmzulGt5A4S5UqDYnWYHT+cuCqzOLGQxZWeT22S 3sUw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:mime-version :references:in-reply-to:message-id:date:subject:cc:to:from :dkim-signature; bh=FZNFa0Som2cEXdyImA0PHzAPIxujgLNI2oeSKx5nHZI=; b=EoAnQfODSUzq14lbK91wWZDtwuvvezJ5U+DEMDWv/4/bLCmvo2qjPX0W3M22vBfTjb F7JKWID2Cvq2fFnmc7l9Q8TmfAMNIZbNWEpcNgleOLKMjkapI4poS1nYR45GgbH+F/jp iMFgiGU0eCivp83QqX5Dfp+hxkZ7LJszwG53JCl6+MaS95BaObpaj2ub8Ip2lTM6Cy4/ HbyG6OuNvRiLP/FHSJQ8RPoLJjXdUsUmy8siTSkQGUbAmwMDoNY9Oq4flbZHl/F5Bv7Z 9Sgkk1D+L08nd24+LZLEGVqUeuPNtCJAL10D6TJIMK8mHoB8hVgEGwkA334AHOGPj4c0 JYOg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@chromium.org header.s=google header.b=h3FquO7M; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=chromium.org Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id s11-20020a056a0008cb00b005752db14951si2116822pfu.218.2022.12.09.08.12.30; Fri, 09 Dec 2022 08:12:42 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@chromium.org header.s=google header.b=h3FquO7M; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=chromium.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229674AbiLIQFc (ORCPT + 75 others); Fri, 9 Dec 2022 11:05:32 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:49710 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229965AbiLIQFF (ORCPT ); Fri, 9 Dec 2022 11:05:05 -0500 Received: from mail-pg1-x531.google.com (mail-pg1-x531.google.com [IPv6:2607:f8b0:4864:20::531]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 670A0554EA for ; Fri, 9 Dec 2022 08:05:04 -0800 (PST) Received: by mail-pg1-x531.google.com with SMTP id h33so3806856pgm.9 for ; Fri, 09 Dec 2022 08:05:04 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=chromium.org; s=google; h=content-transfer-encoding:mime-version:references:in-reply-to :message-id:date:subject:cc:to:from:from:to:cc:subject:date :message-id:reply-to; bh=FZNFa0Som2cEXdyImA0PHzAPIxujgLNI2oeSKx5nHZI=; b=h3FquO7MkL3Xkcl57UR0vuuniHUg5+pjAS+449C9zKHXjh3bfCzGniHHohZYn5ZJxa PimfhG0DETXRYTKLCZGzQghCrFbpOJpZG5Zr0M0bfkbC/VGkO9Ut1cdT7lGwEdufbrrc PnxV8fbesmJTL6d00qwrsh707SkFtLJvebIYI= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=content-transfer-encoding:mime-version:references:in-reply-to :message-id:date:subject:cc:to:from:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=FZNFa0Som2cEXdyImA0PHzAPIxujgLNI2oeSKx5nHZI=; b=rWb5YHTxV/CX8OVOSMIWSD5cWHmQAu8VAOPIbu1HtNc7MgX2VruOxpyT7RLdBnBogV Wzk9aB3psZ3m8ammypGFmrEQswPPLJCVWrgMgJQpQbHQPNuojhH7A5ly8FAWoFmX2nSk lHeUYHLmHgBEarWhwVp21lRIbmcTOsmPqbjGQFcBfyhbDw02uU4VTB3t9k3GMjxLkRei fQNgXKV6rzMWhsQxWD/l9WNRvp3Sx3wgp5WbIYqYWNl3+W5JrPzONqGRSXx3PRXUO1mN Z5awihCvFtTu+DIT8152N70yyLJg1sENfwgCHACQNN4gIl29obz8WmOO+RhkrjtcWSI7 KMdA== X-Gm-Message-State: ANoB5pncgwk47Cc/7aTOh35/EYGGI5KZmKakVNtmrMMyB193yFsTyrg/ qn5/M2GOLkbLQTrQQawWETho2w== X-Received: by 2002:a05:6a00:a05:b0:566:900d:6396 with SMTP id p5-20020a056a000a0500b00566900d6396mr8624787pfh.22.1670601903758; Fri, 09 Dec 2022 08:05:03 -0800 (PST) Received: from jeffxud.c.googlers.com.com (30.202.168.34.bc.googleusercontent.com. [34.168.202.30]) by smtp.gmail.com with ESMTPSA id a15-20020aa795af000000b00576670cc170sm1460504pfk.93.2022.12.09.08.05.02 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Fri, 09 Dec 2022 08:05:03 -0800 (PST) From: jeffxu@chromium.org To: skhan@linuxfoundation.org, keescook@chromium.org Cc: akpm@linux-foundation.org, dmitry.torokhov@gmail.com, dverkamp@chromium.org, hughd@google.com, jeffxu@google.com, jorgelo@chromium.org, linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org, linux-mm@kvack.org, jannh@google.com, linux-hardening@vger.kernel.org, linux-security-module@vger.kernel.org Subject: [PATCH v7 4/6] mm/memfd: Add write seals when apply SEAL_EXEC to executable memfd Date: Fri, 9 Dec 2022 16:04:51 +0000 Message-Id: <20221209160453.3246150-5-jeffxu@google.com> X-Mailer: git-send-email 2.39.0.rc1.256.g54fd8350bd-goog In-Reply-To: <20221209160453.3246150-1-jeffxu@google.com> References: <20221209160453.3246150-1-jeffxu@google.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Spam-Status: No, score=-2.0 required=5.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,RCVD_IN_DNSWL_NONE,SPF_HELO_NONE autolearn=unavailable autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org From: Jeff Xu In order to avoid WX mappings, add F_SEAL_WRITE when apply F_SEAL_EXEC to an executable memfd, so W^X from start. This implys application need to fill the content of the memfd first, after F_SEAL_EXEC is applied, application can no longer modify the content of the memfd. Typically, application seals the memfd right after writing to it. For example: 1. memfd_create(MFD_EXEC). 2. write() code to the memfd. 3. fcntl(F_ADD_SEALS, F_SEAL_EXEC) to convert the memfd to W^X. 4. call exec() on the memfd. Signed-off-by: Jeff Xu Reviewed-by: Kees Cook --- mm/memfd.c | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/mm/memfd.c b/mm/memfd.c index ec70675a7069..92f0a5765f7c 100644 --- a/mm/memfd.c +++ b/mm/memfd.c @@ -222,6 +222,12 @@ static int memfd_add_seals(struct file *file, unsigned int seals) } } + /* + * SEAL_EXEC implys SEAL_WRITE, making W^X from the start. + */ + if (seals & F_SEAL_EXEC && inode->i_mode & 0111) + seals |= F_SEAL_SHRINK|F_SEAL_GROW|F_SEAL_WRITE|F_SEAL_FUTURE_WRITE; + *file_seals |= seals; error = 0; -- 2.39.0.rc1.256.g54fd8350bd-goog