From: Ahmad Fatoum <a.fatoum@pengutronix.de>
To: Fabian Pflug <f.pflug@pengutronix.de>,
BAREBOX <barebox@lists.infradead.org>,
Sascha Hauer <s.hauer@pengutronix.de>
Subject: Re: [PATCH v6 2/7] security: policy: sanity check parameters
Date: Tue, 24 Mar 2026 15:35:53 +0100 [thread overview]
Message-ID: <f466bf28-2cc2-4447-9307-f72e252f50c8@pengutronix.de> (raw)
In-Reply-To: <20260324-v2026-02-0-topic-sconfig_console-v6-2-f0eb6af2cc06@pengutronix.de>
Hi,
On 3/24/26 10:52 AM, Fabian Pflug wrote:
> Do a sanity check for the the is_allowed, before using it as array
> index.
>
> Signed-off-by: Fabian Pflug <f.pflug@pengutronix.de>
> ---
> commands/sconfig.c | 7 ++++++-
> security/policy.c | 2 ++
> 2 files changed, 8 insertions(+), 1 deletion(-)
>
> diff --git a/commands/sconfig.c b/commands/sconfig.c
> index 02c3a6b1ed..3ca4478270 100644
> --- a/commands/sconfig.c
> +++ b/commands/sconfig.c
> @@ -37,7 +37,12 @@ static void sconfig_print(const struct security_policy *policy)
> static int sconfig_command_notify(struct notifier_block *nb,
> unsigned long opt, void *unused)
> {
> - bool allow = is_allowed(NULL, opt);
> + bool allow;
> +
> + if (opt >= SCONFIG_NUM)
> + return 0;
Here you use >=
> +
> + allow = is_allowed(NULL, opt);
>
> printf("%s%s%s%s\n", allow ? green : red, allow ? "+" : "-", nc,
> sconfig_names[opt]);
> diff --git a/security/policy.c b/security/policy.c
> index 85333d9e6f..95e7bf99a2 100644
> --- a/security/policy.c
> +++ b/security/policy.c
> @@ -52,6 +52,8 @@ static bool __is_allowed(const struct security_policy *policy, unsigned option)
> {
> if (!policy)
> return true;
> + if (WARN(option > SCONFIG_NUM))
> + return false;
and here only >
I think you want both to be >= because option is an index?
Thanks,
Ahmad
>
> return policy->policy[option];
> }
>
--
Pengutronix e.K. | |
Steuerwalder Str. 21 | http://www.pengutronix.de/ |
31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
next prev parent reply other threads:[~2026-03-24 14:36 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-24 9:52 [PATCH v6 0/7] Add helper for security policies Fabian Pflug
2026-03-24 9:52 ` [PATCH v6 1/7] of: add of_property_write_string_array() Fabian Pflug
2026-03-24 9:52 ` [PATCH v6 2/7] security: policy: sanity check parameters Fabian Pflug
2026-03-24 14:35 ` Ahmad Fatoum [this message]
2026-03-24 9:52 ` [PATCH v6 3/7] security: policy: remove global active_policy var Fabian Pflug
2026-03-24 9:52 ` [PATCH v6 4/7] security: policy: add notifier chain for name change Fabian Pflug
2026-03-24 9:52 ` [PATCH v6 5/7] common: bootm: add policy to commandline Fabian Pflug
2026-03-24 14:34 ` Ahmad Fatoum
2026-03-24 9:52 ` [PATCH v6 6/7] drivers: pinctrl: configure pinctrl based on policy name Fabian Pflug
2026-03-24 9:52 ` [PATCH v6 7/7] security: kernel_pinctrl: fixup pinctrl in kernel dts Fabian Pflug
2026-03-24 14:57 ` Ahmad Fatoum
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=f466bf28-2cc2-4447-9307-f72e252f50c8@pengutronix.de \
--to=a.fatoum@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=f.pflug@pengutronix.de \
--cc=s.hauer@pengutronix.de \
/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