Linux kernel -stable discussions
 help / color / mirror / Atom feed
From: Fan Wu <wufan@kernel.org>
To: Sasha Levin <sashal@kernel.org>, stable@vger.kernel.org
Subject: Re: [PATCH 6.12.y] ipe: fix use-after-free when auditing a newly loaded policy
Date: Tue, 29 Sep 2026 14:04:48 -0700	[thread overview]
Message-ID: <0533b0b3-160e-447e-b5e1-ff1b3778471b@kernel.org> (raw)
In-Reply-To: <20260929124623.3453618-1-sashal@kernel.org>

On 9/29/2026 5:46 AM, Sasha Levin wrote:
> From: Fan Wu <wufan@kernel.org>
> 
> [ Upstream commit 9814077275eca36ebf8d510d2f076d235ff9f51a ]
> 
> new_policy() audits the policy after ipe_new_policyfs_node() publishes it
> and drops the new directory's inode lock. A concurrent delete can free
> the policy while ipe_audit_policy_load() is still using it.
> 
> Audit the successful load under that lock.
> 
> Fixes: f44554b5067b ("audit,ipe: add IPE auditing support")
> Cc: stable@vger.kernel.org
> Assisted-by: LLM
> [FW: remove model name according to latest guideline]
> Signed-off-by: Fan Wu <wufan@kernel.org>
> [ adapted new_policy() changes to the older success-only auditing implementation. ]
> Signed-off-by: Sasha Levin <sashal@kernel.org>
> ---
>  security/ipe/fs.c        | 4 ----
>  security/ipe/policy_fs.c | 4 ++++
>  2 files changed, 4 insertions(+), 4 deletions(-)
> 
> diff --git a/security/ipe/fs.c b/security/ipe/fs.c
> index 5b6d19fb844a0..d6f90235d6142 100644
> --- a/security/ipe/fs.c
> +++ b/security/ipe/fs.c
> @@ -155,10 +155,6 @@ static ssize_t new_policy(struct file *f, const char __user *data,
>  	}
>  
>  	rc = ipe_new_policyfs_node(p);
> -	if (rc)
> -		goto out;
> -
> -	ipe_audit_policy_load(p);
>  
>  out:
>  	if (rc < 0)
> diff --git a/security/ipe/policy_fs.c b/security/ipe/policy_fs.c
> index 3bcd8cbd09dff..5eba2bb93276f 100644
> --- a/security/ipe/policy_fs.c
> +++ b/security/ipe/policy_fs.c
> @@ -12,6 +12,7 @@
>  #include "policy.h"
>  #include "eval.h"
>  #include "fs.h"
> +#include "audit.h"
>  
>  #define MAX_VERSION_SIZE ARRAY_SIZE("65535.65535.65535")
>  
> @@ -463,6 +464,9 @@ int ipe_new_policyfs_node(struct ipe_policy *p)
>  	inode_lock(root);
>  	p->policyfs = policyfs;
>  	root->i_private = p;
> +	/* Only audit signed policies from userspace */
> +	if (p->pkcs7)
> +		ipe_audit_policy_load(p);
>  	inode_unlock(root);
>  
>  	return 0;

This looks good to me.

Fan

      reply	other threads:[~2026-09-29 21:04 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-29  6:46 FAILED: patch "[PATCH] ipe: fix use-after-free when auditing a newly loaded policy" failed to apply to 6.12-stable tree gregkh
2026-09-29 12:46 ` [PATCH 6.12.y] ipe: fix use-after-free when auditing a newly loaded policy Sasha Levin
2026-09-29 21:04   ` Fan Wu [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=0533b0b3-160e-447e-b5e1-ff1b3778471b@kernel.org \
    --to=wufan@kernel.org \
    --cc=sashal@kernel.org \
    --cc=stable@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox