mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Mike Waychison <mikew@google.com>
Cc: Greg Kroah-Hartman <gregkh@suse.de>,
	Andrew Morton <akpm@linux-foundation.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
	x86@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] x86: Allow disabling of sys_iopl, sys_ioperm
Date: Fri, 15 Jul 2011 10:55:57 +0100	[thread overview]
Message-ID: <20110715105557.7cb3dfcc@lxorguk.ukuu.org.uk> (raw)
In-Reply-To: <CAGTjWtD+5cZxQiE+tikUyz2SNgm3bR95GE2veevEv15cPX1E9A@mail.gmail.com>

> > So lets turn the question around a moment - what breaks if you simply
> > take CAP_SYS_RAWIO away from everything ?
> >
> 
> Alright, I see your point.   ISTR that CAP_SYS_RAWIO was required for
> accessing block devices directly, but this doesn't seem to be the
> case.

Its needed for certain kinds of command issue (raw commands) but not I
believe raw block I/O

> I think the approach I'll try next is to try and drop it with
> PR_CAPBSET_DROP from early userspace's init.
> 
> Any other vectors you would suggest to keep the kiddies away?

/dev/mem /dev/kmem (which do have options to clamp down on)
module loading you have down

GPU if you don't need any graphics. Not so much because its a specific
threat area but because its a large exposure.

For media there are exploit paths to consider where an attacker rewrites
the boot media and reboots. If you need raw disk I/O those are a spot
harder to mend.


  reply	other threads:[~2011-07-15  9:53 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-14 20:34 [PATCH 1/2] Kconfig: Allow disabling of CONFIG_DEVPORT Mike Waychison
2011-07-14 20:34 ` [PATCH 2/2] x86: Allow disabling of sys_iopl, sys_ioperm Mike Waychison
2011-07-14 20:37   ` H. Peter Anvin
2011-07-14 20:38     ` Mike Waychison
2011-07-14 20:40       ` H. Peter Anvin
2011-07-18 14:35         ` Jiri Kosina
2011-07-14 22:31   ` Andrew Morton
2011-07-14 22:35     ` H. Peter Anvin
2011-07-14 22:40       ` Mike Waychison
2011-07-14 22:45         ` H. Peter Anvin
2011-07-14 23:03           ` Alan Cox
2011-07-14 23:04         ` Alan Cox
2011-07-20 19:42         ` Ingo Molnar
2011-07-14 22:42   ` Alan Cox
2011-07-14 22:48     ` Mike Waychison
2011-07-14 23:00       ` Alan Cox
2011-07-14 23:20         ` Mike Waychison
2011-07-14 23:39           ` Alan Cox
2011-07-15  0:48             ` Mike Waychison
2011-07-15  9:55               ` Alan Cox [this message]
2011-07-15 18:13               ` Mike Waychison
2011-07-15 18:14                 ` H. Peter Anvin
2011-07-15 22:30                   ` Andrew G. Morgan
2011-07-15 22:42                     ` Mike Waychison
2011-07-17 23:19                       ` Eric Paris
2011-07-18  0:04                         ` H. Peter Anvin
2011-07-14 21:21 ` [PATCH 1/2] Kconfig: Allow disabling of CONFIG_DEVPORT Greg KH
2011-07-14 22:17   ` Mike Waychison
2011-07-15  6:41     ` Greg KH
2011-07-15 13:13       ` Theodore Tso
2011-07-15 14:51         ` Greg KH
2011-07-15 14:58           ` Alan Cox
2011-07-15 15:19             ` Greg KH
2011-07-15 16:45               ` Mike Waychison
2011-07-15 17:01                 ` Greg KH
2011-07-15 17:51                   ` Mike Waychison
2011-07-15 18:10                     ` H. Peter Anvin
2011-07-15 18:50             ` Andrew Morton
2011-07-15 18:55           ` Ted Ts'o
2011-07-16  7:56             ` Greg KH
2011-07-16 13:05               ` Ted Ts'o
2011-07-16 16:38                 ` Christoph Hellwig

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=20110715105557.7cb3dfcc@lxorguk.ukuu.org.uk \
    --to=alan@lxorguk.ukuu.org.uk \
    --cc=akpm@linux-foundation.org \
    --cc=gregkh@suse.de \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mikew@google.com \
    --cc=mingo@redhat.com \
    --cc=tglx@linutronix.de \
    --cc=x86@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

all inboxes | Powered by JetHome®