From: Mimi Zohar <zohar@linux.ibm.com>
To: Zhao Yipeng <zhaoyipeng5@huawei.com>,
roberto.sassu@huawei.com, dmitry.kasatkin@gmail.com,
eric.snowberg@oracle.com, paul@paul-moore.com, jmorris@namei.org,
serge@hallyn.com, janne.karhunen@gmail.com
Cc: morgan@kernel.org, lujialin4@huawei.com,
linux-integrity@vger.kernel.org,
linux-security-module@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ima: prevent concurrent list operations in ima_lsm_update_rules
Date: Tue, 27 May 2025 15:02:41 -0400 [thread overview]
Message-ID: <f04a8c07d7da1df2cd5b74f04d253611bab9f1ad.camel@linux.ibm.com> (raw)
In-Reply-To: <20250527125103.751077-1-zhaoyipeng5@huawei.com>
On Tue, 2025-05-27 at 20:51 +0800, Zhao Yipeng wrote:
> The current implementation of IMA policy list replacement via
> list_replace_rcu may trigger general protection faults under concurrent
> load policy operations. This occurs when a process replaces a node in
> ima_policy_rules list and sets old->prev = LIST_POISON2, while another
> parallel process still holds references to the old node. Subsequent list
> operations on the poisoned pointer result in kernel panic due to invalid
> memory access.
>
> To resolve this, introduce a mutex lock (ima_rules_mutex) in
> ima_lsm_update_rules() to protect. ima_update_policy() also use the
> ima_policy_rules. Introduce a mutex lock in it.
A new IMA policy may replace the existing builtin policy rules with a custom
policy. In all other cases, the IMA policy rules may only be extended. Writing
or extending the IMA policy rules requires taking the ima_write_mutex.
There's no need for a new mutex.
Mimi
>
> Fixes: b16942455193 ("ima: use the lsm policy update notifier")
> Signed-off-by: Zhao Yipeng <zhaoyipeng5@huawei.com>
> ---
> security/integrity/ima/ima_policy.c | 10 +++++++++-
> 1 file changed, 9 insertions(+), 1 deletion(-)
>
> diff --git a/security/integrity/ima/ima_policy.c
> b/security/integrity/ima/ima_policy.c
> index 128fab897930..d27e615e97d5 100644
> --- a/security/integrity/ima/ima_policy.c
> +++ b/security/integrity/ima/ima_policy.c
> @@ -471,6 +471,8 @@ static bool ima_rule_contains_lsm_cond(struct
> ima_rule_entry *entry)
> return false;
> }
>
> +static DEFINE_MUTEX(ima_rules_mutex);
> +
> /*
> * The LSM policy can be reloaded, leaving the IMA LSM based rules referring
> * to the old, stale LSM policy. Update the IMA LSM based rules to reflect
> @@ -481,16 +483,19 @@ static void ima_lsm_update_rules(void)
> struct ima_rule_entry *entry, *e;
> int result;
>
> + mutex_lock(&ima_rules_mutex);
> list_for_each_entry_safe(entry, e, &ima_policy_rules, list) {
> if (!ima_rule_contains_lsm_cond(entry))
> continue;
>
> result = ima_lsm_update_rule(entry);
> if (result) {
> + mutex_unlock(&ima_rules_mutex);
> pr_err("lsm rule update error %d\n", result);
> return;
> }
> }
> + mutex_unlock(&ima_rules_mutex);
> }
>
> int ima_lsm_policy_change(struct notifier_block *nb, unsigned long event,
> @@ -1038,9 +1043,12 @@ int ima_check_policy(void)
> */
> void ima_update_policy(void)
> {
> - struct list_head *policy = &ima_policy_rules;
> + struct list_head *policy;
>
> + mutex_lock(&ima_rules_mutex);
> + policy = &ima_policy_rules;
> list_splice_tail_init_rcu(&ima_temp_rules, policy, synchronize_rcu);
> + mutex_unlock(&ima_rules_mutex);
>
> if (ima_rules != (struct list_head __rcu *)policy) {
> ima_policy_flag = 0;
prev parent reply other threads:[~2025-05-27 19:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-27 12:51 [PATCH] ima: prevent concurrent list operations in ima_lsm_update_rules Zhao Yipeng
2025-05-27 19:02 ` Mimi Zohar [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=f04a8c07d7da1df2cd5b74f04d253611bab9f1ad.camel@linux.ibm.com \
--to=zohar@linux.ibm.com \
--cc=dmitry.kasatkin@gmail.com \
--cc=eric.snowberg@oracle.com \
--cc=janne.karhunen@gmail.com \
--cc=jmorris@namei.org \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=lujialin4@huawei.com \
--cc=morgan@kernel.org \
--cc=paul@paul-moore.com \
--cc=roberto.sassu@huawei.com \
--cc=serge@hallyn.com \
--cc=zhaoyipeng5@huawei.com \
/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;
as well as URLs for NNTP newsgroup(s).