All of lore.kernel.org
 help / color / mirror / Atom feed
From: ebiederm@xmission.com (Eric W. Biederman)
To: Dan Carpenter <dan.carpenter@oracle.com>
Cc: linux-kernel@vger.kernel.org, kernel-hardening@lists.openwall.com
Subject: Re: [kernel-hardening] 2015 kernel CVEs
Date: Tue, 19 Jan 2016 16:47:32 -0600	[thread overview]
Message-ID: <87ziw14263.fsf@x220.int.ebiederm.org> (raw)
In-Reply-To: <20160119112812.GA10818@mwanda> (Dan Carpenter's message of "Tue, 19 Jan 2016 14:28:12 +0300")

Dan Carpenter <dan.carpenter@oracle.com> writes:

> 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.
>
> CVE-2015-8709 : ptrace: race in user namespaces let's users trace root processes

As this isn't a kernel bug, and is not a race, and no one has even
bothered to see if any userspace processes are this stupid I don't even
think that qualifies as a CVE.

There is room for improvement in this area but I don't see how this
qualifies as a CVE.

So for doing better I recommend a little more vetting and paying
attention before assigning CVEs.

Eric

  parent reply	other threads:[~2016-01-19 22:56 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-19 11:28 2015 kernel CVEs Dan Carpenter
2016-01-19 11:28 ` [kernel-hardening] " Dan Carpenter
2016-01-19 11:49 ` Hanno Böck
2016-01-19 15:49   ` Quentin Casasnovas
2016-01-20 11:19   ` Hanno Böck
2016-01-20 14:15     ` Wade Mealing
2016-01-20 17:48       ` Hanno Böck
2016-01-19 13:13 ` Wade Mealing
2016-01-19 14:56 ` One Thousand Gnomes
2016-01-19 14:56   ` [kernel-hardening] " One Thousand Gnomes
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 16:57   ` [kernel-hardening] " Peter Hurley
2016-01-19 17:00   ` Josh Boyer
2016-01-19 17:00     ` [kernel-hardening] " Josh Boyer
2016-01-19 17:51     ` Greg KH
2016-01-19 17:51       ` [kernel-hardening] " Greg KH
2016-01-20  7:12       ` Marcus Meissner
2016-01-19 17:57 ` [kernel-hardening] " Theodore Ts'o
2016-01-19 18:00 ` Al Viro
2016-01-19 18:00   ` [kernel-hardening] " Al Viro
2016-01-19 22:41   ` Eric W. Biederman
2016-01-19 22:47 ` Eric W. Biederman [this message]
2016-01-20 20:11   ` [kernel-hardening] " Jann Horn
2016-01-20 21:26     ` One Thousand Gnomes
2016-01-19 23:35 ` Kees Cook
2016-01-19 23:35   ` Kees Cook
2016-01-20  9:57 ` Miroslav Benes
2016-01-20  9:57   ` [kernel-hardening] " 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=87ziw14263.fsf@x220.int.ebiederm.org \
    --to=ebiederm@xmission.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.