From: sashiko-bot@kernel.org
Cc: selinux@vger.kernel.org
Subject: Re: [PATCH 4/5] selinux: validate user MLS range and default level at load
Date: Thu, 03 Sep 2026 11:52:36 +0000 [thread overview]
Message-ID: <20260903115236.BF94F1F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260903113538.72942-3-cgoettsche@seltendoof.de>
> From: Christian Göttsche <cgzones@googlemail.com>
>
> user_read() reads each user's MLS range and default level but, unlike
> range transitions and security contexts, never validates them.
> Validate usr->range and usr->dfltlevel in user_index_check() when MLS is
> enabled, once the level and category symbol tables are populated.
>
> Signed-off-by: Christian Göttsche <cgzones@googlemail.com>
Sashiko has reviewed this patch and found no issues. It looks great!
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260903113538.72942-1-cgoettsche@seltendoof.de?part=4
next prev parent reply other threads:[~2026-09-03 11:52 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-03 11:35 [PATCH 2/5] selinux: bounds-check filename transition source types at load Christian Göttsche
2026-09-03 11:35 ` [PATCH 3/5] selinux: bounds-check role and user membership bitmaps " Christian Göttsche
2026-09-03 11:55 ` sashiko-bot
2026-09-03 13:50 ` Stephen Smalley
2026-09-03 11:35 ` [PATCH 4/5] selinux: validate user MLS range and default level " Christian Göttsche
2026-09-03 11:52 ` sashiko-bot [this message]
2026-09-03 13:52 ` Stephen Smalley
2026-09-03 11:35 ` [PATCH 5/5] selinux: validate permissive and neveraudit map types " Christian Göttsche
2026-09-03 11:50 ` sashiko-bot
2026-09-03 13:53 ` Stephen Smalley
2026-09-03 11:35 ` [PATCH 1/5] selinux: reject duplicate symbol values during policy load Christian Göttsche
2026-09-03 11:57 ` sashiko-bot
2026-09-03 13:44 ` Stephen Smalley
2026-09-03 11:52 ` [PATCH 2/5] selinux: bounds-check filename transition source types at load sashiko-bot
2026-09-03 13:47 ` Stephen Smalley
2026-09-03 15:18 ` Christian Göttsche
2026-09-04 12:10 ` Stephen Smalley
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=20260903115236.BF94F1F000E9@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.