Reply-To: kernel-hardening@lists.openwall.com Date: Tue, 19 Jan 2016 09:51:54 -0800 From: Greg KH Message-ID: <20160119175154.GA7485@kroah.com> References: <20160119112812.GA10818@mwanda> <569E6ADC.2090306@hurleysoftware.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Subject: [kernel-hardening] Re: 2015 kernel CVEs To: Josh Boyer Cc: Peter Hurley , Dan Carpenter , "Linux-Kernel@Vger. Kernel. Org" , kernel-hardening@lists.openwall.com List-ID: On Tue, Jan 19, 2016 at 12:00:57PM -0500, Josh Boyer wrote: > On Tue, Jan 19, 2016 at 11:57 AM, Peter Hurley wrote: > > On 01/19/2016 03:28 AM, Dan Carpenter 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. > > > > [...] > > > >> CVE-2015-4170 cf872776fc84: tty: hang in tty > > > > Makes no sense that this was assigned a CVE. > > I fixed this _2 yrs before_ it was reported and the patch was CC'd stable. > > I'm guessing the CVE was assigned because there are distributions that > ship based on kernels earlier than 3.13. Those distributors need to > verify if they have the fix, etc. Yes, that's what happened here, Red Hat asked for it from what I remember. I complained loudly on the oss-security list about it, but oh well... greg k-h