linux-kernel - Re: [PATCH 2/2] mm/mmap.c: do not allow mappings outside of allowed limits

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-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <20200420195903.93455e087985b423f97bdfe3@linux-foundation.org>
Date:   Mon, 20 Apr 2020 19:59:03 -0700
From:   Andrew Morton <akpm@...ux-foundation.org>
To:     agordeev@...ux.ibm.com
Cc:     linux-kernel@...r.kernel.org, linux-mm@...ck.org
Subject: Re: [PATCH 2/2] mm/mmap.c: do not allow mappings outside of allowed
 limits

On Mon, 23 Mar 2020 14:29:29 +0100 agordeev@...ux.ibm.com wrote:

> It is possible to request a fixed mapping address below
> mmap_min_addr and succeed. This update adds early checks
> of mmap_min_addr and mmap_end boundaries and fixes the
> above issue.

Does this solve any known problems?  If not, what is the motivation for
the change?