Received: by 2002:a25:ef43:0:0:0:0:0 with SMTP id w3csp132313ybm; Tue, 26 May 2020 12:34:38 -0700 (PDT) X-Google-Smtp-Source: ABdhPJwOSvI37Uz9MEUWCK5xtYJZadWFgvBH4AvRXAJPRcrbdtxKwJhvIywxWGJIFZTflbD0GLsH X-Received: by 2002:a17:906:f9d7:: with SMTP id lj23mr2731075ejb.218.1590521678648; Tue, 26 May 2020 12:34:38 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1590521678; cv=none; d=google.com; s=arc-20160816; b=B12Czem0RaGQdLYvgzYXwsJEvMyrxwW0iekE1Pa8OSMgE4wjXOY28djU108RRK5cXc AEP6f19kvlfJzyTqNo2WZ/9c3pxCBqxpYx7kEhH/WQTg2mIbxXHSvIKcg4C+Q0qcJz1D nDwxdppFqsQCn/Hy6HVjUUtDPVCon7YswF01ZK8k36MVlnJLRxyJouwqCLBLvZJAJvxB vZL7nTcsMGz9WPFoG6l//MIqZcTtFE9vF9lP7GTInt6n5C8qZMeWNqZVTaucp2RrNDga fTeqhCpE8hM4Aam7wKgIDhXmHu9QwERpHw619d3RcN2cJT8res1zxV8v0A04QO1R944V +RsA== 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=OlsfahR4MX4GHKwXhoHm0toL4YsA9LSQtpyJNhXrSso=; b=BC+qXT5QvRBFG0YcLtjlQbgJq5wLrzg8OM8TH3uMCE0pms7wVhQixkaj8aPkpL1OVc SzxjKrpwQJ/Dlz3qHN1y+wVrW+knUZNrRZ9Ybhqk+bfXxEXaXlZlfnrHpQYlB1LPkpl+ EG5Oqp5H8BoxcSAFJc7dgoAx1NSu3d2gkoAsWzr7lmkMQRP+/gIztYec3eyoq6umqc/W ZD1VTEyK2P6daFFNtW3/pLrBnwAgJ1nXExW3ELTBTae9NnV+72BiWuutXbBQk9SyBans jPehgF7L3p83kEsxaXbFRC4FpTM+WgW7FuX8cwGEfS2tSL2zijf/8MZ/whKGNEF2kzOU sMQw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=ndv3rf0N; 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 k22si412947eja.706.2020.05.26.12.34.15; Tue, 26 May 2020 12:34:38 -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=ndv3rf0N; 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 S2390409AbgEZS6t (ORCPT + 99 others); Tue, 26 May 2020 14:58:49 -0400 Received: from mail.kernel.org ([198.145.29.99]:52328 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S2390400AbgEZS6s (ORCPT ); Tue, 26 May 2020 14:58:48 -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 4B84B2084C; Tue, 26 May 2020 18:58:47 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1590519527; bh=NggTwWB4h5a6XcBcy4V/G/PG1JIy21Q8VRrMocZwruQ=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=ndv3rf0NjJmdlxDd++6CN2dQWGadwVSHG7UzUQvY0D0HcjJRCerTU0/sIBb+CXqPp 4QGTdQPkIsYzPbo6itXeBRsMLugW4qKunbZJmyKaSTwbEdsca52WMy2/Mqsm4Ty4d8 smzxWWpVpFbpo+P7TSEYxFfRfGCbqL8AiZWr+I+A= 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.9 07/64] ima: Fix return value of ima_write_policy() Date: Tue, 26 May 2020 20:52:36 +0200 Message-Id: <20200526183915.613897186@linuxfoundation.org> X-Mailer: git-send-email 2.26.2 In-Reply-To: <20200526183913.064413230@linuxfoundation.org> References: <20200526183913.064413230@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 44b44d7e0dbc..853a7d2333b3 100644 --- a/security/integrity/ima/ima_fs.c +++ b/security/integrity/ima/ima_fs.c @@ -331,8 +331,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