Received: by 2002:a25:ef43:0:0:0:0:0 with SMTP id w3csp131220ybm; Tue, 26 May 2020 12:33:08 -0700 (PDT) X-Google-Smtp-Source: ABdhPJz9HRlk/827KqRCRS+HGBE61b7MTjVWfSONTr5WX/XKzskxLH4yAYUAaQEbWX8dO5O5/D9P X-Received: by 2002:a17:906:454a:: with SMTP id s10mr2445827ejq.112.1590521588690; Tue, 26 May 2020 12:33:08 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1590521588; cv=none; d=google.com; s=arc-20160816; b=0hwsAZcEMgGY6B8+QbDESCXjlHur8jcg/m7vfE/Av0BLf69cRqdXRdYus6FtCKON3F YyFXUOTz2UGuqLVVR8yprJE/E3zrjmOVkHLl0mN19c/MR7PmjlJAEjQsCCMzmcMbHeBG DVBv6cFrDpOswpsqlIRDeIN76rUbGyNH/V2ZlSdEqmqypZnt/PoeJLpkdMHNMWyNHoaZ ZxzWDSzaWkDg2Tg8JNoMh+RguxvfyYUCRZCydWSBxNIrA8BolPwLUEbqNKYcE+w2qDXd E0tUb6UYFieQSoYerMdCj8cPDSwREw+OVh/JRDBlvJnrHFp8qCGAzhv6dl/V1l+asXbk fd2w== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:mime-version :user-agent:references:in-reply-to:message-id:date:subject:cc:to :from:dkim-signature; bh=OitiiRcARM9DUEzloE9e4UC6jAjIQA3YbWP4iiYV2t4=; b=fB8HngeDsOdPWo35VFPBBTQyHN2DVB2tbibbfF+nU9hC7tDNT9hQ5lEKqlX9TsKxgs P8JnF/wbKc+QUu6HpBIM3wI/LeDRUsuaX0HpEfmbXggic/SqsGct2w696auswgm7ilp+ kTZEn/cEUljchTSiEHXuqolqEM4nANtbiprXp/vZLAu7oXD/3QlUWtcqtjIV4dReCua1 JfKIDtfWzaWAjhd4kz7IUognNTdevV/qbpbfiUljBJO+Jzxs+OBrzOEPR3yqxXPXQztS UWcnX5oEhsIZIIZrV9skxNaqGo98Z/E3iXygOmzKVgUw+xPYscx64JRQ/N37jrWO6eJz gMUw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=Ccf5vE5M; 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 Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id g8si449213ejb.85.2020.05.26.12.32.44; Tue, 26 May 2020 12:33:08 -0700 (PDT) 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=@kernel.org header.s=default header.b=Ccf5vE5M; 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 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2390908AbgEZTBS (ORCPT + 99 others); Tue, 26 May 2020 15:01:18 -0400 Received: from mail.kernel.org ([198.145.29.99]:55566 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S2390911AbgEZTBQ (ORCPT ); Tue, 26 May 2020 15:01:16 -0400 Received: from localhost (83-86-89-107.cable.dynamic.v4.ziggo.nl [83.86.89.107]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id BEAA82086A; Tue, 26 May 2020 19:01:15 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1590519676; bh=jxpV9bwZNr00uF7Pt1uZ/SNrypyG2VMQGrhaC84nUkg=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=Ccf5vE5Mq84fOKCLoc1tZ8AH/5wZy8rH98yVE9iQmse8PYsMVmpE9HmIVbYyfiCtL soLCSJdws52SoTZ64IKXy6J1xU2m0W65UgpUzXUq1ZRthu4ldTN/7VrOub1PDwjxDG F9FdgSRfNpS292+Qab5KuI+JNqv3DGjFKaNGNyR4= From: Greg Kroah-Hartman To: linux-kernel@vger.kernel.org Cc: Greg Kroah-Hartman , stable@vger.kernel.org, Roberto Sassu , Krzysztof Struczynski , Mimi Zohar , Sasha Levin Subject: [PATCH 4.14 08/59] ima: Fix return value of ima_write_policy() Date: Tue, 26 May 2020 20:52:53 +0200 Message-Id: <20200526183910.008888439@linuxfoundation.org> X-Mailer: git-send-email 2.26.2 In-Reply-To: <20200526183907.123822792@linuxfoundation.org> References: <20200526183907.123822792@linuxfoundation.org> User-Agent: quilt/0.66 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org From: Roberto Sassu [ Upstream commit 2e3a34e9f409ebe83d1af7cd2f49fca7af97dfac ] This patch fixes the return value of ima_write_policy() when a new policy is directly passed to IMA and the current policy requires appraisal of the file containing the policy. Currently, if appraisal is not in ENFORCE mode, ima_write_policy() returns 0 and leads user space applications to an endless loop. Fix this issue by denying the operation regardless of the appraisal mode. Cc: stable@vger.kernel.org # 4.10.x Fixes: 19f8a84713edc ("ima: measure and appraise the IMA policy itself") Signed-off-by: Roberto Sassu Reviewed-by: Krzysztof Struczynski Signed-off-by: Mimi Zohar Signed-off-by: Sasha Levin --- security/integrity/ima/ima_fs.c | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/security/integrity/ima/ima_fs.c b/security/integrity/ima/ima_fs.c index 2c4e83f6409e..d37f9ac46670 100644 --- a/security/integrity/ima/ima_fs.c +++ b/security/integrity/ima/ima_fs.c @@ -340,8 +340,7 @@ static ssize_t ima_write_policy(struct file *file, const char __user *buf, integrity_audit_msg(AUDIT_INTEGRITY_STATUS, NULL, NULL, "policy_update", "signed policy required", 1, 0); - if (ima_appraise & IMA_APPRAISE_ENFORCE) - result = -EACCES; + result = -EACCES; } else { result = ima_parse_add_rule(data); } -- 2.25.1