linux-security-module.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mimi Zohar <zohar@linux.ibm.com>
To: Roberto Sassu <roberto.sassu@huaweicloud.com>,
	viro@zeniv.linux.org.uk, brauner@kernel.org, jack@suse.cz,
	dmitry.kasatkin@gmail.com, eric.snowberg@oracle.com,
	paul@paul-moore.com, jmorris@namei.org, serge@hallyn.com
Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-integrity@vger.kernel.org,
	linux-security-module@vger.kernel.org,
	Roberto Sassu <roberto.sassu@huawei.com>
Subject: Re: [PATCH v2 3/7] ima: Ensure lock is held when setting iint pointer in inode security blob
Date: Tue, 14 Jan 2025 09:20:39 -0500	[thread overview]
Message-ID: <3545a38326a5d3dff28b1089ab2149f1662a641b.camel@linux.ibm.com> (raw)
In-Reply-To: <20241128100621.461743-4-roberto.sassu@huaweicloud.com>

On Thu, 2024-11-28 at 11:06 +0100, Roberto Sassu wrote:
> From: Roberto Sassu <roberto.sassu@huawei.com>
> 
> IMA stores a pointer of the ima_iint_cache structure, containing integrity
> metadata, in the inode security blob. However, check and assignment of this
> pointer is not atomic, and it might happen that two tasks both see that the
> iint pointer is NULL and try to set it, causing a memory leak.
> 
> Ensure that the iint check and assignment is guarded, by adding a lockdep
> assertion in ima_inode_get().

-> is guarded by the ima_iint_cache_lock mutex, ...

> 
> Consequently, guard the remaining ima_inode_get() calls, in
> ima_post_create_tmpfile() and ima_post_path_mknod(), to avoid the lockdep
> warnings.
> 
> Signed-off-by: Roberto Sassu <roberto.sassu@huawei.com>
> ---
>  security/integrity/ima/ima_iint.c |  2 ++
>  security/integrity/ima/ima_main.c | 14 ++++++++++++--
>  2 files changed, 14 insertions(+), 2 deletions(-)
> 
> diff --git a/security/integrity/ima/ima_iint.c b/security/integrity/ima/ima_iint.c
> index dcc32483d29f..fca9db293c79 100644
> --- a/security/integrity/ima/ima_iint.c
> +++ b/security/integrity/ima/ima_iint.c
> @@ -97,6 +97,8 @@ struct ima_iint_cache *ima_inode_get(struct inode *inode)
>  	if (!iint_lock)
>  		return NULL;
>  
> +	lockdep_assert_held(&iint_lock->mutex);
> +

lockdep_assert_held() doesn't actually "ensure" the lock is held, but emits a warning
when the lock is not held (if debugging is enabled).  Semantically "ensure" gives the
impression of enforcing.

Mimi

>  	iint = iint_lock->iint;
>  	if (iint)
>  		return iint;
> diff --git a/security/integrity/ima/ima_main.c b/security/integrity/ima/ima_main.c
> index 05cfb04cd02b..1e474ff6a777 100644
> --- a/security/integrity/ima/ima_main.c
> +++ b/security/integrity/ima/ima_main.c
> @@ -705,14 +705,19 @@ static void ima_post_create_tmpfile(struct mnt_idmap *idmap,
>  	if (!must_appraise)
>  		return;
>  
> +	ima_iint_lock(inode);
> +
>  	/* Nothing to do if we can't allocate memory */
>  	iint = ima_inode_get(inode);
> -	if (!iint)
> +	if (!iint) {
> +		ima_iint_unlock(inode);
>  		return;
> +	}
>  
>  	/* needed for writing the security xattrs */
>  	set_bit(IMA_UPDATE_XATTR, &iint->atomic_flags);
>  	iint->ima_file_status = INTEGRITY_PASS;
> +	ima_iint_unlock(inode);
>  }
>  
>  /**
> @@ -737,13 +742,18 @@ static void ima_post_path_mknod(struct mnt_idmap *idmap,
> struct dentry *dentry)
>  	if (!must_appraise)
>  		return;
>  
> +	ima_iint_lock(inode);
> +
>  	/* Nothing to do if we can't allocate memory */
>  	iint = ima_inode_get(inode);
> -	if (!iint)
> +	if (!iint) {
> +		ima_iint_unlock(inode);
>  		return;
> +	}
>  
>  	/* needed for re-opening empty files */
>  	iint->flags |= IMA_NEW_FILE;
> +	ima_iint_unlock(inode);
>  }
>  
>  /**


  reply	other threads:[~2025-01-14 14:21 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-28 10:06 [PATCH v2 0/7] ima: Remove unnecessary inode locks Roberto Sassu
2024-11-28 10:06 ` [PATCH v2 1/7] fs: ima: Remove S_IMA and IS_IMA() Roberto Sassu
2024-11-28 11:40   ` Jan Kara
2024-11-28 13:30   ` Christian Brauner
2024-11-28 10:06 ` [PATCH v2 2/7] ima: Remove inode lock Roberto Sassu
2025-01-14 13:35   ` Mimi Zohar
2025-01-15 10:45     ` Roberto Sassu
2024-11-28 10:06 ` [PATCH v2 3/7] ima: Ensure lock is held when setting iint pointer in inode security blob Roberto Sassu
2025-01-14 14:20   ` Mimi Zohar [this message]
2025-01-15 10:51     ` Roberto Sassu
2024-11-28 10:06 ` [PATCH v2 4/7] ima: Mark concurrent accesses to the iint pointer in the " Roberto Sassu
2025-01-14 14:32   ` Mimi Zohar
2024-11-28 10:06 ` [PATCH v2 5/7] ima: Set security.ima on file close when ima_appraise=fix Roberto Sassu
2025-01-15 13:46   ` Mimi Zohar
2025-01-17 17:06     ` Roberto Sassu
2024-11-28 10:06 ` [PATCH v2 6/7] ima: Discard files opened with O_PATH Roberto Sassu
2024-11-28 16:22   ` Christian Brauner
2024-11-28 16:25     ` Roberto Sassu
2025-01-16 11:52   ` Mimi Zohar
2024-11-28 10:06 ` [PATCH v2 7/7] ima: Reset IMA_NONACTION_RULE_FLAGS after post_setattr Roberto Sassu
2025-01-16 13:12   ` Mimi Zohar

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=3545a38326a5d3dff28b1089ab2149f1662a641b.camel@linux.ibm.com \
    --to=zohar@linux.ibm.com \
    --cc=brauner@kernel.org \
    --cc=dmitry.kasatkin@gmail.com \
    --cc=eric.snowberg@oracle.com \
    --cc=jack@suse.cz \
    --cc=jmorris@namei.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-integrity@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-security-module@vger.kernel.org \
    --cc=paul@paul-moore.com \
    --cc=roberto.sassu@huawei.com \
    --cc=roberto.sassu@huaweicloud.com \
    --cc=serge@hallyn.com \
    --cc=viro@zeniv.linux.org.uk \
    /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).