mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: kernel-hardening@lists.openwall.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: [kernel-hardening] 2015 kernel CVEs
Date: Tue, 19 Jan 2016 09:54:09 -0800	[thread overview]
Message-ID: <20160119175409.GB7485@kroah.com> (raw)
In-Reply-To: <1453221128.3734.26.camel@decadent.org.uk>

On Tue, Jan 19, 2016 at 04:32:08PM +0000, Ben Hutchings wrote:
> As for USB descriptors, I'm somewhat more hopeful about hardening.  At
> the same time, it seems like it should be practical to put more low-
> performance USB drivers into userspace.

What drivers do we currently have in the kernel that should/could be
done in userspace instead?  I'll gladly drop them from the tree.

And yes, we need to do better about handling crazy USB descriptors, I
think the majority of this work is already done, but it takes
hand-auditing to verify it :(

thanks,

greg k-h

  reply	other threads:[~2016-01-19 17:54 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20160119124917.6058019b@pc1>
2016-01-19 11:28 ` Dan Carpenter
2016-01-19 14:56   ` One Thousand Gnomes
2016-01-19 16:32   ` [kernel-hardening] " Ben Hutchings
2016-01-19 17:54     ` Greg KH [this message]
2016-01-20 17:05       ` Ben Hutchings
2016-01-20 18:04         ` Greg KH
2016-01-21 15:18           ` Jiri Kosina
2016-01-21 18:46           ` Ben Hutchings
2016-01-19 16:57   ` Peter Hurley
2016-01-19 17:00     ` Josh Boyer
2016-01-19 17:51       ` Greg KH
2016-01-20  7:12         ` [kernel-hardening] " Marcus Meissner
2016-01-19 17:57   ` [kernel-hardening] " Theodore Ts'o
2016-01-19 18:00   ` Al Viro
2016-01-19 22:41     ` [kernel-hardening] " Eric W. Biederman
2016-01-19 22:47   ` [kernel-hardening] " Eric W. Biederman
2016-01-20 20:11     ` Jann Horn
2016-01-20 21:26       ` One Thousand Gnomes
2016-01-19 23:35   ` Kees Cook
2016-01-20  9:57   ` Miroslav Benes

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=20160119175409.GB7485@kroah.com \
    --to=greg@kroah.com \
    --cc=kernel-hardening@lists.openwall.com \
    --cc=linux-kernel@vger.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
Powered by JetHome