Re: thoughts on kernel security issues
From: Matt Mackall (mpm_at_selenic.com)
Date: 01/13/05
- Previous message: William Lee Irwin III: "Re: thoughts on kernel security issues"
- In reply to: Andrew Morton: "Re: thoughts on kernel security issues"
- Next in thread: Linus Torvalds: "Re: thoughts on kernel security issues"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Wed, 12 Jan 2005 23:25:58 -0800 To: Andrew Morton <akpm@osdl.org>
On Wed, Jan 12, 2005 at 10:54:12PM -0800, Andrew Morton wrote:
> William Lee Irwin III <wli@holomorphy.com> wrote:
> >
> > Most of the local DoS's I'm aware of are memory management -related,
> > i.e. user- triggerable proliferation of pinned kernel data structures.
>
> Well. A heck of a lot of the DoS opportunities we've historically seen
> involved memory leaks, deadlocks or making the kernel go oops or BUG with
> locks held or with kernel memory allocated.
I think we can probably exclude root-only local DoS from the full
embargo treatment for starters. The recent /dev/random sysctl one was
in that category.
I can imagine some local DoS bugs that are worth keeping a lid on for
a bit. Classic F00F bug may have been a good example. But hole in an
arbitrary driver may not.
-- Mathematics is the supreme nostalgia of our time. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
- Previous message: William Lee Irwin III: "Re: thoughts on kernel security issues"
- In reply to: Andrew Morton: "Re: thoughts on kernel security issues"
- Next in thread: Linus Torvalds: "Re: thoughts on kernel security issues"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
