Received: by 2002:a05:6a10:22f:0:0:0:0 with SMTP id 15csp3759846pxk; Tue, 29 Sep 2020 05:43:23 -0700 (PDT) X-Google-Smtp-Source: ABdhPJxl1RujbvvJm6RTFkzMx48vDPCTVW8vpjiSVnYNbiiq4+P/ryPaOOE4fjOXe5UHNJDReYUk X-Received: by 2002:a17:906:6682:: with SMTP id z2mr3838472ejo.434.1601383403003; Tue, 29 Sep 2020 05:43:23 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1601383402; cv=none; d=google.com; s=arc-20160816; b=gg9uw81jwFxgNvpBfWVsdgXVFkNNYpAH8Yuk+RcGUp8d0iR+7ijt/dyONspayPEJ/O GChJv1AEP8Wb38RhQDvim0IjCqJr1SVPvwpB74QE23trgMvORPZ9qp6ePmcLHsWpgP9l AbFLy/v85pYUAQaY7UpBMiLQhdNOdAM2KmBl/navmmQXjKeRE/cAJs/ZzWh+mJJcdr0T mPlTaCgJrMlX+zCQYpNwZEVDgOCFOOlJSlY7eWmUM6dDj9z4jcSJvRpMKtf3165S4nlY aJFiX4Fp+uOAQMJALWjLnnHkX3bG6I/r5ag/MYQ/aYBAW/xso/vOTsN2jF8KV48iwnL7 h8mw== 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 :user-agent:references:in-reply-to:message-id:date:subject:cc:to :from:dkim-signature; bh=xudz/ShWD/l6KTjQaComkI5g8bbvV9LRADKUqcF6zak=; b=GEDHJ8TLRug8xvY1gl1rhqmMnRMGeupCj29P+uJXJTUJfMkUgMiUuQdO0OkytEgFj2 vdWNKvi4zegLVwFpaZFfFNyFWpeaaPVWSQxwrnRDsc8FbrQg0B85j47tVRh4/ghaeuIF CtzV1RjuCW0AGWxqgKXLPGy+w15T8mKNmMy9na9YJYvDG0Nqt4Evj5Ete5xrzCdZon9n HVDVbxskdO33NkRUQV/grqIKYm5cb1+JddOVGo/i6XJgsuQ8Vh99szLF6qB+IaRIBH+h 3COMX/gVnOQgNPaH3qKNZv9soEALIQKf+46yzpQCvonDe6oSQ1vSkfMTy1jV71SHNukd 6v5w== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=0zetuUP2; 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; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=linuxfoundation.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id dc21si1092479edb.373.2020.09.29.05.42.59; Tue, 29 Sep 2020 05:43:22 -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=0zetuUP2; 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; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=linuxfoundation.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1730488AbgI2MkE (ORCPT + 99 others); Tue, 29 Sep 2020 08:40:04 -0400 Received: from mail.kernel.org ([198.145.29.99]:32838 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1729578AbgI2LQT (ORCPT ); Tue, 29 Sep 2020 07:16:19 -0400 Received: from localhost (83-86-74-64.cable.dynamic.v4.ziggo.nl [83.86.74.64]) (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 5BE3F206DB; Tue, 29 Sep 2020 11:16:18 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1601378179; bh=1A9kQmECskEl4gPJ+6UrYq13lluTiE+z2WhigvhzBpM=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=0zetuUP2pFURImGIABe9RjRK120Cia/SnhIibU08BiES/UdZkbAA3KX4QYMEBg3EL 4RKrvFYwZ/nTaqFXrsGES8Z4wIR6UWXwRSLAVObUdnZK47tVPgt/Pvllp9zqA78IBh ofbkeLZpAH6L1MoLRIDC7oGDpGQFuO310+ddlatM= From: Greg Kroah-Hartman To: linux-kernel@vger.kernel.org Cc: Greg Kroah-Hartman , stable@vger.kernel.org, Steve Grubb , Paul Moore , Sasha Levin Subject: [PATCH 4.14 060/166] audit: CONFIG_CHANGE dont log internal bookkeeping as an event Date: Tue, 29 Sep 2020 12:59:32 +0200 Message-Id: <20200929105938.216049161@linuxfoundation.org> X-Mailer: git-send-email 2.28.0 In-Reply-To: <20200929105935.184737111@linuxfoundation.org> References: <20200929105935.184737111@linuxfoundation.org> User-Agent: quilt/0.66 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org From: Steve Grubb [ Upstream commit 70b3eeed49e8190d97139806f6fbaf8964306cdb ] Common Criteria calls out for any action that modifies the audit trail to be recorded. That usually is interpreted to mean insertion or removal of rules. It is not required to log modification of the inode information since the watch is still in effect. Additionally, if the rule is a never rule and the underlying file is one they do not want events for, they get an event for this bookkeeping update against their wishes. Since no device/inode info is logged at insertion and no device/inode information is logged on update, there is nothing meaningful being communicated to the admin by the CONFIG_CHANGE updated_rules event. One can assume that the rule was not "modified" because it is still watching the intended target. If the device or inode cannot be resolved, then audit_panic is called which is sufficient. The correct resolution is to drop logging config_update events since the watch is still in effect but just on another unknown inode. Signed-off-by: Steve Grubb Signed-off-by: Paul Moore Signed-off-by: Sasha Levin --- kernel/audit_watch.c | 2 -- 1 file changed, 2 deletions(-) diff --git a/kernel/audit_watch.c b/kernel/audit_watch.c index 35f1d706bd5b4..ac87820cc0825 100644 --- a/kernel/audit_watch.c +++ b/kernel/audit_watch.c @@ -316,8 +316,6 @@ static void audit_update_watch(struct audit_parent *parent, if (oentry->rule.exe) audit_remove_mark(oentry->rule.exe); - audit_watch_log_rule_change(r, owatch, "updated_rules"); - call_rcu(&oentry->rcu, audit_free_rule_rcu); } -- 2.25.1