linux-kernel - Re: [PATCH] mm: kmemleak: take a full lowmem check in kmemleak_*

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: <20220413122826.792a859d90b6c2822b1c796a@linux-foundation.org>
Date:   Wed, 13 Apr 2022 12:28:26 -0700
From:   Andrew Morton <akpm@...ux-foundation.org>
To:     Patrick Wang <patrick.wang.shcn@...il.com>
Cc:     catalin.marinas@....com, linux-mm@...ck.org,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH] mm: kmemleak: take a full lowmem check in
 kmemleak_*_phys()

On Wed, 13 Apr 2022 20:29:25 +0800 Patrick Wang <patrick.wang.shcn@...il.com> wrote:

> The kmemleak_*_phys() apis do not check the address for lowmem's min
> boundary, while the caller may pass an address below lowmem, which
> will trigger an oops:

Do you believe this fix should be backported into -stable kernels?