public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dan Rosenberg <drosenberg@vsecurity.com>
To: Richard Weinberger <richard@nod.at>
Cc: akpm@linux-foundation.org, mingo@elte.hu, davem@davemloft.net,
	dzickus@redhat.com, randy.dunlap@oracle.com,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Restrict write access to dmesg_restrict
Date: Mon, 14 Mar 2011 15:49:55 -0400	[thread overview]
Message-ID: <1300132195.2194.6.camel@dan> (raw)
In-Reply-To: <1300131356-24389-1-git-send-email-richard@nod.at>

On Mon, 2011-03-14 at 20:35 +0100, Richard Weinberger wrote:
> When dmesg_restrict is set to 1 CAP_SYS_ADMIN is needed
> to read the kernel ring buffer.
> But a root user without CAP_SYS_ADMIN is able to reset
> dmesg_restrict to 0.

A minor correction, CAP_SYSLOG is needed to read the kernel syslog.  But
I think requiring CAP_SYS_ADMIN is appropriate to modify the value of
the sysctl, so assuming the commit message reflects this:

Acked-by: Dan Rosenberg <drosenberg@vsecurity.com>

> 
> This is an issue when e.g. LXC (Linux Containers) are used
> and complete user space is running without CAP_SYS_ADMIN.
> A unprivileged and jailed root user can bypass the
> dmesg_restrict protection.
> 
> With this patch writing to dmesg_restrict is only allowed
> when root has CAP_SYS_ADMIN.
> 
> Signed-off-by: Richard Weinberger <richard@nod.at>
> ---
>  kernel/sysctl.c |   18 +++++++++++++++++-
>  1 files changed, 17 insertions(+), 1 deletions(-)
> 
> diff --git a/kernel/sysctl.c b/kernel/sysctl.c
> index 4eed0af..f90c8f6 100644
> --- a/kernel/sysctl.c
> +++ b/kernel/sysctl.c
> @@ -169,6 +169,11 @@ static int proc_taint(struct ctl_table *table, int write,
>  			       void __user *buffer, size_t *lenp, loff_t *ppos);
>  #endif
>  
> +#ifdef CONFIG_PRINTK
> +static int proc_dmesg_restrict(struct ctl_table *table, int write,
> +				void __user *buffer, size_t *lenp, loff_t *ppos);
> +#endif
> +
>  #ifdef CONFIG_MAGIC_SYSRQ
>  /* Note: sysrq code uses it's own private copy */
>  static int __sysrq_enabled = SYSRQ_DEFAULT_ENABLE;
> @@ -704,7 +709,7 @@ static struct ctl_table kern_table[] = {
>  		.data		= &dmesg_restrict,
>  		.maxlen		= sizeof(int),
>  		.mode		= 0644,
> -		.proc_handler	= proc_dointvec_minmax,
> +		.proc_handler	= proc_dmesg_restrict,
>  		.extra1		= &zero,
>  		.extra2		= &one,
>  	},
> @@ -2397,6 +2402,17 @@ static int proc_taint(struct ctl_table *table, int write,
>  	return err;
>  }
>  
> +#ifdef CONFIG_PRINTK
> +static int proc_dmesg_restrict(struct ctl_table *table, int write,
> +				void __user *buffer, size_t *lenp, loff_t *ppos)
> +{
> +	if (write && !capable(CAP_SYS_ADMIN))
> +		return -EPERM;
> +
> +	return proc_dointvec_minmax(table, write, buffer, lenp, ppos);
> +}
> +#endif
> +
>  struct do_proc_dointvec_minmax_conv_param {
>  	int *min;
>  	int *max;
> -- 
> 1.6.6.1



  reply	other threads:[~2011-03-14 19:50 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-14 19:35 [PATCH] Restrict write access to dmesg_restrict Richard Weinberger
2011-03-14 19:49 ` Dan Rosenberg [this message]
2011-03-14 20:02   ` Richard Weinberger
2011-03-15 13:46 ` WANG Cong

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=1300132195.2194.6.camel@dan \
    --to=drosenberg@vsecurity.com \
    --cc=akpm@linux-foundation.org \
    --cc=davem@davemloft.net \
    --cc=dzickus@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=randy.dunlap@oracle.com \
    --cc=richard@nod.at \
    /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