linux-kernel - [PATCH 0/3] properly account for stack randomization and guard gap

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-Id: <20170622200033.25714-1-riel@redhat.com>
Date:   Thu, 22 Jun 2017 16:00:30 -0400
From:   riel@...hat.com
To:     linux-kernel@...r.kernel.org
Cc:     akpm@...ux-foundation.org, mingo@...nel.org, will.deacon@....com,
        danielmicay@...il.com, benh@...nel.crashing.org, hughd@...gle.com
Subject: [PATCH 0/3] properly account for stack randomization and guard gap

When RLIMIT_STACK is larger than the minimum gap enforced by
mmap_base(), it is possible for the kernel to place the mmap
area where the stack wants to grow, resulting in the stack
not being able to use the space that should have been allocated
to it through RLIMIT_STACK.

This series ensures that x86, ARM64, and PPC have at least
RLIMIT_STACK + stack randomization + the stack guard gap
space available for the stack.

s390 seems to be ok. I have not checked other architectures.