There were a few commits added for CVE-2017-1000364:
a010365 mm/mmap.c: expand_downwards: don't require the gap if !vm_prev
8105a5d mm/mmap.c: do not blow on PROT_NONE MAP_FIXED holes in the stack
028383b Allow stack to grow up to address space limit
393d9b1 mm: fix new crash in unmapped_area_topdown()
88a1685 mm: larger stack guard gap, between vmas
cf83f7c mm: vma_adjust: remove superfluous confusing update in remove_next == 1 case
I'd like to build some test kernels, each with peeling of one of these commits at a time to try and narrow down which one caused it.
I built the first test kernel with commit a010365 reverted.
There were a few commits added for CVE-2017-1000364:
a010365 mm/mmap.c: expand_downwards: don't require the gap if !vm_prev area_topdown( )
8105a5d mm/mmap.c: do not blow on PROT_NONE MAP_FIXED holes in the stack
028383b Allow stack to grow up to address space limit
393d9b1 mm: fix new crash in unmapped_
88a1685 mm: larger stack guard gap, between vmas
cf83f7c mm: vma_adjust: remove superfluous confusing update in remove_next == 1 case
I'd like to build some test kernels, each with peeling of one of these commits at a time to try and narrow down which one caused it.
I built the first test kernel with commit a010365 reverted.
The test kernel can be downloaded from: kernel. ubuntu. com/~jsalisbury /lp1699772
http://
Can you test this kernel and see if it resolves this bug?
Note, to test this kernel, you need to install both the linux-image and linux-image-extra .deb packages.
Thanks in advance!