blob: db4983bd43b92d7e29df928714b1320f7c0d3735 (
plain) (
blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
|
Description: mmap'd regions including ld.so data segment may be close to stack limit
References:
https://www.qualys.com/2017/06/19/stack-clash/stack-clash.txt
Notes:
bwh> It's unclear to me whether this deserves a specific fix, separate
bwh> from that for CVE-2017-1000364.
carnil> It's unclear wich of the stack-clash patchset patches fixes the
carnil> issue in specific.
jmm> Red Hat, Ubuntu and SuSE all closed this bug with a reference that it's
jmm> fixed along with the other fixes, shall we just do the same?
Bugs:
upstream: released (4.12-rc6) [1be7107fbe18eed3e319a6c3e83c78254b693acb]
4.9-upstream-stable: released (4.9.34) [cfc0eb403816c5c4f9667d959de5e22789b5421e]
3.16-upstream-stable: released (3.16.45) [978b8aa1646d4e023edd121c7f1b8f938ccb813d]
3.2-upstream-stable: ignored "EOL"
sid: released (4.11.6-1) [bugfix/all/mm-larger-stack-guard-gap-between-vmas.patch]
4.9-stretch-security: released (4.9.30-2+deb9u1)
3.16-jessie-security: released (3.16.43-2+deb8u1)
3.2-wheezy-security: ignored "EOL"
|
