From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Dan Carpenter <dan.carpenter@oracle.com>
Cc: Alexander Holler <holler@ahsoftware.de>,
Dave Jones <davej@redhat.com>, Kees Cook <keescook@chromium.org>,
"Theodore Ts'o" <tytso@mit.edu>,
vegard.nossum@oracle.com, LKML <linux-kernel@vger.kernel.org>,
Tommi Rantala <tt.rantala@gmail.com>,
Ingo Molnar <mingo@kernel.org>,
"Eric W. Biederman" <ebiederm@xmission.com>,
Andy Lutomirski <luto@amacapital.net>,
Daniel Vetter <daniel.vetter@ffwll.ch>,
Alan Cox <alan@linux.intel.com>, Jason Wang <jasowang@redhat.com>,
"David S. Miller" <davem@davemloft.net>,
James Morris <james.l.morris@oracle.com>
Subject: Re: [PATCH 1/9] Known exploit detection
Date: Fri, 13 Dec 2013 03:57:38 -0800 [thread overview]
Message-ID: <20131213115738.GA17838@kroah.com> (raw)
In-Reply-To: <20131213114841.GA5443@mwanda>
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
next prev parent reply other threads:[~2013-12-13 11:55 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-12 16:52 [PATCH 1/9] Known exploit detection vegard.nossum
2013-12-12 16:52 ` [PATCH 2/9] exploit: report to audit subsystem when available vegard.nossum
2013-12-12 16:52 ` [PATCH 3/9] hfs: Known exploit detection for CVE-2011-4330 vegard.nossum
2013-12-13 8:00 ` Dan Carpenter
2013-12-12 16:52 ` [PATCH 4/9] net: Known exploit detection for CVE-2012-2136 vegard.nossum
2013-12-12 16:52 ` [PATCH 5/9] hfsplus: Known exploit detection for CVE-2012-2319 vegard.nossum
2013-12-13 1:40 ` Greg Kroah-Hartman
2013-12-13 11:14 ` One Thousand Gnomes
2013-12-12 16:52 ` [PATCH 6/9] x86: Known exploit detection for CVE-2013-0268 vegard.nossum
2013-12-12 16:52 ` [PATCH 7/9] drm/i915: Known exploit detection for CVE-2013-0913 vegard.nossum
2013-12-12 16:52 ` [PATCH 8/9] userns: Known exploit detection for CVE-2013-1959 vegard.nossum
2013-12-12 16:52 ` [PATCH 9/9] perf: Known exploit detection for CVE-2013-2094 vegard.nossum
2013-12-12 19:06 ` [PATCH 1/9] Known exploit detection Theodore Ts'o
2013-12-12 21:13 ` Kees Cook
2013-12-12 23:50 ` Ryan Mallon
2013-12-12 23:55 ` Kees Cook
2013-12-13 11:10 ` One Thousand Gnomes
2013-12-13 14:21 ` Jiri Kosina
2013-12-13 9:20 ` Vegard Nossum
2013-12-13 22:49 ` Ryan Mallon
2013-12-13 13:06 ` Ingo Molnar
2013-12-13 15:55 ` Jason Cooper
2013-12-13 23:07 ` Ryan Mallon
2013-12-13 0:25 ` Dave Jones
2013-12-13 0:45 ` Andy Lutomirski
2013-12-13 1:42 ` Greg Kroah-Hartman
2013-12-13 1:44 ` Dave Jones
2013-12-13 5:09 ` James Morris
2013-12-13 5:46 ` Theodore Ts'o
2013-12-13 13:19 ` Ingo Molnar
2013-12-13 10:21 ` Vegard Nossum
2013-12-13 10:31 ` Alexander Holler
2013-12-13 11:48 ` Dan Carpenter
2013-12-13 11:57 ` Greg Kroah-Hartman [this message]
2013-12-13 13:23 ` Ingo Molnar
2013-12-13 18:00 ` Kees Cook
2013-12-13 17:58 ` Kees Cook
2013-12-13 18:14 ` Linus Torvalds
2013-12-13 18:37 ` Kees Cook
2013-12-13 5:27 ` Theodore Ts'o
2013-12-13 9:32 ` Jiri Kosina
2013-12-13 18:07 ` Kees Cook
2013-12-13 9:12 ` Vegard Nossum
2013-12-13 13:27 ` Ingo Molnar
2013-12-13 8:20 ` Vegard Nossum
2013-12-14 23:59 ` Ryan Mallon
2013-12-13 12:54 ` Ingo Molnar
2013-12-16 5:17 ` Sasha Levin
2013-12-19 6:14 ` David Rientjes
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=20131213115738.GA17838@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=alan@linux.intel.com \
--cc=dan.carpenter@oracle.com \
--cc=daniel.vetter@ffwll.ch \
--cc=davej@redhat.com \
--cc=davem@davemloft.net \
--cc=ebiederm@xmission.com \
--cc=holler@ahsoftware.de \
--cc=james.l.morris@oracle.com \
--cc=jasowang@redhat.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=mingo@kernel.org \
--cc=tt.rantala@gmail.com \
--cc=tytso@mit.edu \
--cc=vegard.nossum@oracle.com \
/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