linux-kernel - Re: [PATCH -next] x86/efi_64: fix a user-memory-access in runtime

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: <934E6F23-96FE-4C59-9387-9ABA2959DBBB@lca.pw>
Date:   Sat, 18 Jan 2020 06:04:30 -0500
From:   Qian Cai <cai@....pw>
To:     Ard Biesheuvel <ard.biesheuvel@...aro.org>
Cc:     Ard Biesheuvel <ardb@...nel.org>, Ingo Molnar <mingo@...hat.com>,
        kasan-dev <kasan-dev@...glegroups.com>,
        linux-efi <linux-efi@...r.kernel.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH -next] x86/efi_64: fix a user-memory-access in runtime



> On Jan 18, 2020, at 3:00 AM, Ard Biesheuvel <ard.biesheuvel@...aro.org> wrote:
> 
> Can't we just use READ_ONCE_NOCHECK() instead?

My understanding is that KASAN actually want to make sure there is a no dereference of user memory because it has security implications. Does that make no sense here?