[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20131213114841.GA5443@mwanda>
Date: Fri, 13 Dec 2013 14:48:41 +0300
From: Dan Carpenter <dan.carpenter@...cle.com>
To: Alexander Holler <holler@...oftware.de>
Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
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 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.
You are right that probably some security commits don't get a CVE. When
you spot one then feel free to ask for a CVE from the
oss-security@...ts.openwall.com email list.
regards,
dan carpenter
--
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