From: Jeff Layton <jlayton@kernel.org>
To: Ondrej Mosnacek <omosnace@redhat.com>, Paul Moore <paul@paul-moore.com>
Cc: David Howells <dhowells@redhat.com>,
Christian Brauner <brauner@kernel.org>,
selinux@vger.kernel.org, linux-fsdevel@vger.kernel.org,
Adam Williamson <awilliam@redhat.com>
Subject: Re: [PATCH] selinux: fix handling of empty opts in selinux_fs_context_submount()
Date: Mon, 11 Sep 2023 15:33:48 -0400 [thread overview]
Message-ID: <11597d56bbb44a83fcbce8d1161068dd96a41ec4.camel@kernel.org> (raw)
In-Reply-To: <20230911142358.883728-1-omosnace@redhat.com>
On Mon, 2023-09-11 at 16:23 +0200, Ondrej Mosnacek wrote:
> selinux_set_mnt_opts() relies on the fact that the mount options pointer
> is always NULL when all options are unset (specifically in its
> !selinux_initialized() branch. However, the new
> selinux_fs_context_submount() hook breaks this rule by allocating a new
> structure even if no options are set. That causes any submount created
> before a SELinux policy is loaded to be rejected in
> selinux_set_mnt_opts().
>
> Fix this by making selinux_fs_context_submount() leave fc->security
> set to NULL when there are no options to be copied from the reference
> superblock.
>
> Reported-by: Adam Williamson <awilliam@redhat.com>
> Link: https://bugzilla.redhat.com/show_bug.cgi?id=2236345
> Fixes: d80a8f1b58c2 ("vfs, security: Fix automount superblock LSM init problem, preventing NFS sb sharing")
> Signed-off-by: Ondrej Mosnacek <omosnace@redhat.com>
> ---
> security/selinux/hooks.c | 10 ++++++++--
> 1 file changed, 8 insertions(+), 2 deletions(-)
>
> diff --git a/security/selinux/hooks.c b/security/selinux/hooks.c
> index 10350534de6d6..2aa0e219d7217 100644
> --- a/security/selinux/hooks.c
> +++ b/security/selinux/hooks.c
> @@ -2775,14 +2775,20 @@ static int selinux_umount(struct vfsmount *mnt, int flags)
> static int selinux_fs_context_submount(struct fs_context *fc,
> struct super_block *reference)
> {
> - const struct superblock_security_struct *sbsec;
> + const struct superblock_security_struct *sbsec = selinux_superblock(reference);
> struct selinux_mnt_opts *opts;
>
> + /*
> + * Ensure that fc->security remains NULL when no options are set
> + * as expected by selinux_set_mnt_opts().
> + */
> + if (!(sbsec->flags & (FSCONTEXT_MNT|CONTEXT_MNT|DEFCONTEXT_MNT)))
> + return 0;
> +
> opts = kzalloc(sizeof(*opts), GFP_KERNEL);
> if (!opts)
> return -ENOMEM;
>
> - sbsec = selinux_superblock(reference);
> if (sbsec->flags & FSCONTEXT_MNT)
> opts->fscontext_sid = sbsec->sid;
> if (sbsec->flags & CONTEXT_MNT)
Reviewed-by: Jeff Layton <jlayton@kernel.org>
next prev parent reply other threads:[~2023-09-11 20:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-11 14:23 [PATCH] selinux: fix handling of empty opts in selinux_fs_context_submount() Ondrej Mosnacek
2023-09-11 19:33 ` Jeff Layton [this message]
2023-09-12 21:31 ` Paul Moore
2023-09-13 7:51 ` Christian Brauner
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=11597d56bbb44a83fcbce8d1161068dd96a41ec4.camel@kernel.org \
--to=jlayton@kernel.org \
--cc=awilliam@redhat.com \
--cc=brauner@kernel.org \
--cc=dhowells@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=omosnace@redhat.com \
--cc=paul@paul-moore.com \
--cc=selinux@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;
as well as URLs for NNTP newsgroup(s).