[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20131213115738.GA17838@kroah.com>
Date: Fri, 13 Dec 2013 03:57:38 -0800
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: Dan Carpenter <dan.carpenter@...cle.com>
Cc: Alexander Holler <holler@...oftware.de>,
Dave Jones <davej@...hat.com>,
Kees Cook <keescook@...omium.org>,
Theodore Ts'o <tytso@....edu>, vegard.nossum@...cle.com,
LKML <linux-kernel@...r.kernel.org>,
Tommi Rantala <tt.rantala@...il.com>,
Ingo Molnar <mingo@...nel.org>,
"Eric W. Biederman" <ebiederm@...ssion.com>,
Andy Lutomirski <luto@...capital.net>,
Daniel Vetter <daniel.vetter@...ll.ch>,
Alan Cox <alan@...ux.intel.com>,
Jason Wang <jasowang@...hat.com>,
"David S. Miller" <davem@...emloft.net>,
James Morris <james.l.morris@...cle.com>
Subject: Re: [PATCH 1/9] Known exploit detection
On Fri, Dec 13, 2013 at 02:48:41PM +0300, Dan Carpenter wrote:
> On Fri, Dec 13, 2013 at 11:31:48AM +0100, Alexander Holler wrote:
> > I've never seen a comment inside the kernel sources which does point
> > to a CVE, so I assume there already does exists some agreement about
> > not doing so.
>
> We do occasionally put CVE numbers in the commit message, but normally
> the commit comes first before we ask for a CVE number.
>
> If you want a list of kernel CVEs then you can use the Ubuntu list:
> https://launchpad.net/ubuntu-cve-tracker
> http://people.canonical.com/~ubuntu-security/cve/main.html
> It has the commit which introduced the bug and commit which fixes the
> bug. Suse has a public CVE list as well.
There is a project underway to track fixes for CVE issues in the kernel,
and to corrispond them with the patch that resolves them, as well as
when (if at all) they enter the various stable kernel releases.
That should make tracking this type of thing easier over time, and is
more comprehensive than the Ubuntu list.
But that's getting off-topic here a bit, sorry...
greg k-h
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists