Openwall GNU/*/Linux - a small security-enhanced Linux distro for servers
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Fri, 20 Jan 2017 15:51:35 +0100
From: Greg KH <greg@...ah.com>
To: oss-security@...ts.openwall.com
Cc: Jesse Hertz <Jesse.Hertz@...group.trust>,
	Wade Mealing <wmealing@...hat.com>
Subject: Re: CVE REQUEST: linux kernel: process with pgid zero
 able to crash kernel

On Fri, Jan 20, 2017 at 09:01:17AM -0500, Brad Spengler wrote:
> Hi Greg,
> 
> Much like you feel it's not your job to inform your own users of 
> vulnerabilities you've silently fixed, it's not the job of distros (who 
> are actually informing their own users) to do your job of determining 
> what kernels a particular fix affects, particularly when you just use it 
> as a way of getting your advertisement out there that people should be 
> running the latest Linux kernels.

I've never claimed that it was their job, I was just asking to try to
get an idea of where the issue was and when it was fixed to ensure that
the users of the LTS kernels were ok.  How is that a bad thing?

> Of course, what you're missing is that when it's the distros
> themselves requesting the CVEs, this skews the discussion of
> vulnerabilities to older kernels, not the much higher number present
> in the latest upstream "stable".

That's fine with me, I have no objection to that, never have.

> While we're here, how about a CVE for a recent kernel, for a vulnerability
> not fixed in any stable kernel yet, and introduced for a pointless mitigation
> no less:
> https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=c4e490cf148e85ead0d1b1c2caaba833f1d5b29f
> This affects upstream >= 4.8 when CONFIG_SLAB_FREELIST_RANDOM is enabled
> ("for those following along at home")
> 
> Or, since VMAP_STACK was introduced haphazardly in 4.9 without doing any 
> static analysis beyond a simple grep or smatch it seems, there are probably a 
> dozen or so DoSes when CONFIG_DEBUG_SG or CONFIG_DEBUG_VIRTUAL is 
> enabled, or potential silent or not so silent memory corruption when 
> it's not, as a scatterlist crossing a virtual page boundary will then 
> end up accessing a totally unrelated adjacent physical page if a stack 
> address was passed into the scatterlist, and these vulnerabilities will 
> continue to pop up until something comprehensive is done to prevent 
> them.  Emese's written an IPA GCC plugin to find all the ones you've missed,
> so we know there still are many that haven't been fixed.
> http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=6d104af38b570d37aa32a5803b04c354f8ed513d 
> https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=a45f795c65b479b4ba107b6ccde29b896d51ee98
> https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=06deeec77a5a689cc94b21a8a91a76e42176685d
> 0day alert, not fixed in 4.9 yet:
> https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=05a974efa4bdf6e2a150e3f27dc6fcf0a9ad5655
> Not to mention the bugs introduced via fixes for VMAP_STACK:
> https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=146cc8a17a3b4996f6805ee5c080e7101277c410
> 
> Or how about a CVE for this huge heap infoleak (and while I'm at it, congrats to
> Al for not covering it up for once, maybe he's learning!):
> http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=b9dc6f65bc5e232d1c05fe34b5daadc7e8bbf1fb
> Or this (sgid bit not cleared on tmpfs):
> http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=497de07d89c1410d76a15bec2bb41f24a2a89f31

Many thanks for the list, I've queued up the few that I had missed in
previous stable kernel updates, or were not already in my queue for
future releases, it is much appreciated.

greg k-h

Powered by blists - more mailing lists

Your e-mail address:

Please check out the Open Source Software Security Wiki, which is counterpart to this mailing list.

Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.