mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: One Thousand Gnomes <gnomes@lxorguk.ukuu.org.uk>
To: Dan Carpenter <dan.carpenter@oracle.com>
Cc: linux-kernel@vger.kernel.org, kernel-hardening@lists.openwall.com
Subject: Re: 2015 kernel CVEs
Date: Tue, 19 Jan 2016 14:56:09 +0000	[thread overview]
Message-ID: <20160119145609.1238be62@lxorguk.ukuu.org.uk> (raw)
In-Reply-To: <20160119112812.GA10818@mwanda>

On Tue, 19 Jan 2016 14:28:12 +0300
Dan Carpenter <dan.carpenter@oracle.com> wrote:

> I like to look back over old CVEs to see how we could do better.  Here
> is the list from 2015.  I got most of this information from the Ubuntu
> CVE tracker.  Thanks Ubuntu!.  If it doesn't have a hash that means it
> might not be fixed yet.

That's the list of bugs originating in 2015. You need to go back further
to see some of the fun ones still present (CVE-2013-7445 for example)

> There was only a coupls CVEs that looks like they came from a filesystem
> fuzzer where you create a corrupt filesystems and then try use them.
> There was only one that might have come from a USB fuzzer.  We probably
> should be testing those things better.

There are a bunch of those ignored in Bugzilla for years. I think the
ones for the mainstream file systems have all been tackled but things
like reiserfs don't survive fuzzing too well, which is a problem if your
distribution naïvely builds in automounting support for people rooting
your box via USB stick.

Alan

  reply	other threads:[~2016-01-19 14:56 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 [this message]
2016-01-19 16:32   ` [kernel-hardening] " Ben Hutchings
2016-01-19 17:54     ` Greg KH
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=20160119145609.1238be62@lxorguk.ukuu.org.uk \
    --to=gnomes@lxorguk.ukuu.org.uk \
    --cc=dan.carpenter@oracle.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