linux-hardening - Re: [PATCH] lkdtm/usercopy: Expand size of "out of frame" object

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 for Android: free password hash cracker in your pocket

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

Date:   Fri, 18 Feb 2022 15:30:35 +0500
From:   Muhammad Usama Anjum <usama.anjum@...labora.com>
To:     Kees Cook <keescook@...omium.org>
Cc:     usama.anjum@...labora.com, Arnd Bergmann <arnd@...db.de>,
        Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
        linux-kernel@...r.kernel.org, linux-hardening@...r.kernel.org
Subject: Re: [PATCH] lkdtm/usercopy: Expand size of "out of frame" object


On 2/17/22 1:17 AM, Kees Cook wrote:
> To be sufficient out of range for the usercopy test to see the lifetime
> mismatch, expand the size of the "bad" buffer, which will let it be
> beyond current_stack_pointer regardless of stack growth direction.
> Paired with the recent addition of stack depth checking under
> CONFIG_HARDENED_USERCOPY=y, this will correctly start tripping again.
> 
> Reported-by: Muhammad Usama Anjum <usama.anjum@...labora.com>
> Cc: Arnd Bergmann <arnd@...db.de>
> Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
> Signed-off-by: Kees Cook <keescook@...omium.org>
Reviewed-by: Muhammad Usama Anjum <usama.anjum@...labora.com>