Received: by 2002:a25:ef43:0:0:0:0:0 with SMTP id w3csp262941ybm; Tue, 26 May 2020 16:19:14 -0700 (PDT) X-Google-Smtp-Source: ABdhPJzllXAnEhUcRicnB1fS6Dux09zeq39R53DK3mxG+Na6wQsIAimXb1EqffoDpXjBBLLhivlD X-Received: by 2002:a17:906:7e17:: with SMTP id e23mr3147129ejr.172.1590535154288; Tue, 26 May 2020 16:19:14 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1590535154; cv=none; d=google.com; s=arc-20160816; b=Z01UgPnCQUaPf63TJ2xJ6eAvA4dAUZHUJux4WlnZPeT0pDa9L+D0tQHEM50LsL4fyt l99Otz1H67WvQWEvvYgqOwNNUuBxQR0VQoky0PVe90dMTp4/VzLytiZBQ7uIF9vL41st jSE5Ms+vUIE+ydtqcpXEP5qwMK/H9ieakHb1NraXvX03Knvrx9CY1MD/PIxejao7/ye6 HSCj6/sxJIqhHJkz9p+regNJ91XpseUjF/O5POOJvrZNUFDD5rrCcjBeiAim3eqUpOq8 keHoN0iPQBAfMIbdl6B45wKTLX82VR9jMrP/wRRzCDWeBkxHA3RGgs8YOp9VLQ8EK0R/ TGdg== 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=BOLcc6Ce+xXBF0eJmPVdp+PrheEC5+Etk+B6x9g1cjM=; b=VPBZ54KXSqQZqb5xfbJPRYo89kMXgynkTPHwaPVf0MCI5wSoLxOASB4YX53fKS/E25 GbLP3Ae3hunjLaAva3U2Wey/ByuIdDNl6Mr6Yl90EwjE1dkQDwy6M8NUzxWk9Rhp8AUH kMG4L4RicUCrztXu/uLu43VB8apYeK1EMW8Z+nSl5qDMynr/Y/YYGogb/oGbMxsBTYYT kbsRDlgcCP5uH/V2PwlFgRhV2+HOh2XM+5IqNqQ1vPBIj4YenLuOwBj0z8qecPKXFdR9 15NMQR/2hao8EoqftHTZEds1jYfVw81sNRKSVmrrOj+YUoNKI0X3y/we4j8WKcFTIeAS nOSA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=KF1nOoAH; 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 de21si687529edb.304.2020.05.26.16.18.51; Tue, 26 May 2020 16:19:14 -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=KF1nOoAH; 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 S2392036AbgEZTZF (ORCPT + 99 others); Tue, 26 May 2020 15:25:05 -0400 Received: from mail.kernel.org ([198.145.29.99]:35746 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S2391698AbgEZTHJ (ORCPT ); Tue, 26 May 2020 15:07:09 -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 72D17208B3; Tue, 26 May 2020 19:07:08 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1590520028; bh=TjVIzJCh0CEfsQLND/3pcn51jPC8iMMpkKt8EVaLwEw=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=KF1nOoAHWv6uPtZjkSnYqlA2ZMmzvG34aV4rRPVVGtk+p3IlAsxqfOO36xelTUNMw HDm9e3CygUiT50CVFT7TR+zur2FJCxKO6WsoIpRU0/nT8VSqR8VV/LUdyYKMdVcEee DyzWpWDBhE5L3q8NtVTPsdgWAkxm+h96DnyjmOnU= 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 5.4 005/111] ima: Fix return value of ima_write_policy() Date: Tue, 26 May 2020 20:52:23 +0200 Message-Id: <20200526183932.953352409@linuxfoundation.org> X-Mailer: git-send-email 2.26.2 In-Reply-To: <20200526183932.245016380@linuxfoundation.org> References: <20200526183932.245016380@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 2000e8df0301..68571c40d61f 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