linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Rafael Aquini <aquini@redhat.com>
Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
	mcgrof@kernel.org, keescook@chromium.org, yzaikin@google.com,
	tytso@mit.edu
Subject: Re: [PATCH] kernel: sysctl: ignore out-of-range taint bits introduced via kernel.tainted
Date: Tue, 12 May 2020 13:53:26 -0700	[thread overview]
Message-ID: <20200512135326.49daaa924b1fa2fb694e2d74@linux-foundation.org> (raw)
In-Reply-To: <20200512174653.770506-1-aquini@redhat.com>

On Tue, 12 May 2020 13:46:53 -0400 Rafael Aquini <aquini@redhat.com> wrote:

> The sysctl knob

/proc/sys/kernel/tainted, yes?

> allows users with SYS_ADMIN capability to
> taint the kernel with any arbitrary value, but this might
> produce an invalid flags bitset being committed to tainted_mask.
> 
> This patch introduces a simple way for proc_taint() to ignore
> any eventual invalid bit coming from the user input before
> committing those bits to the kernel tainted_mask.
> 
> ...
>
> --- a/include/linux/kernel.h
> +++ b/include/linux/kernel.h
> @@ -597,6 +597,8 @@ extern enum system_states {
>  #define TAINT_RANDSTRUCT		17
>  #define TAINT_FLAGS_COUNT		18
>  
> +#define TAINT_FLAGS_MAX			((1UL << TAINT_FLAGS_COUNT) - 1)
> +
>  struct taint_flag {
>  	char c_true;	/* character printed when tainted */
>  	char c_false;	/* character printed when not tainted */
> diff --git a/kernel/sysctl.c b/kernel/sysctl.c
> index 8a176d8727a3..fb2d693fc08c 100644
> --- a/kernel/sysctl.c
> +++ b/kernel/sysctl.c
> @@ -2623,11 +2623,23 @@ static int proc_taint(struct ctl_table *table, int write,
>  		return err;
>  
>  	if (write) {
> +		int i;
> +
> +		/*
> +		 * Ignore user input that would cause the loop below
> +		 * to commit arbitrary and out of valid range TAINT flags.
> +		 */
> +		if (tmptaint > TAINT_FLAGS_MAX) {
> +			tmptaint &= TAINT_FLAGS_MAX;
> +			pr_warn_once("%s: out-of-range taint input ignored."
> +				     " tainted_mask adjusted to 0x%lx\n",
> +				     __func__, tmptaint);
> +		}
> +
>  		/*
>  		 * Poor man's atomic or. Not worth adding a primitive
>  		 * to everyone's atomic.h for this
>  		 */
> -		int i;
>  		for (i = 0; i < BITS_PER_LONG && tmptaint >> i; i++) {

Could simply replace BITS_PER_LONG with TAINT_FLAGS_COUNT here?

(That "&& tmptaint >> i" seems a rather silly optimization?)

>  			if ((tmptaint >> i) & 1)
>  				add_taint(i, LOCKDEP_STILL_OK);

In fact the whole thing could be simplified down to

	for (i = 1; i <= TAINT_FLAGS_COUNT; i <<= 1)
		if (i & tmptaint)
			add_taint(...)

and silently drop out-of-range bits?

  reply	other threads:[~2020-05-12 20:53 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-12 17:46 [PATCH] kernel: sysctl: ignore out-of-range taint bits introduced via kernel.tainted Rafael Aquini
2020-05-12 20:53 ` Andrew Morton [this message]
2020-05-12 21:13   ` Rafael Aquini
2020-05-12 22:31 ` Luis Chamberlain

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=20200512135326.49daaa924b1fa2fb694e2d74@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=aquini@redhat.com \
    --cc=keescook@chromium.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mcgrof@kernel.org \
    --cc=tytso@mit.edu \
    --cc=yzaikin@google.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).