linux-kernel - Re: [PATCH v2] lkdtm: Add kfence read after free crash type

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

Message-Id: <170138194305.3650163.16392122923355361827.b4-ty@chromium.org>
Date:   Thu, 30 Nov 2023 14:05:45 -0800
From:   Kees Cook <keescook@...omium.org>
To:     Stephen Boyd <swboyd@...omium.org>
Cc:     Kees Cook <keescook@...omium.org>, linux-kernel@...r.kernel.org,
        patches@...ts.linux.dev, Arnd Bergmann <arnd@...db.de>,
        Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
        Alexander Potapenko <glider@...gle.com>,
        Marco Elver <elver@...gle.com>,
        Dmitry Vyukov <dvyukov@...gle.com>,
        Andrew Morton <akpm@...ux-foundation.org>,
        kasan-dev@...glegroups.com
Subject: Re: [PATCH v2] lkdtm: Add kfence read after free crash type

On Wed, 29 Nov 2023 13:44:04 -0800, Stephen Boyd wrote:
> Add the ability to allocate memory from kfence and trigger a read after
> free on that memory to validate that kfence is working properly. This is
> used by ChromeOS integration tests to validate that kfence errors can be
> collected on user devices and parsed properly.
> 
> 

Applied to for-next/hardening, thanks!

[1/1] lkdtm: Add kfence read after free crash type
      https://git.kernel.org/kees/c/0e689e666214

Take care,

-- 
Kees Cook