linux-kernel - Re: [PATCH] base/node.c: initialize the accessor list before registering

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: <2023103129-coming-geometric-8ac0@gregkh>
Date:   Tue, 31 Oct 2023 07:03:17 +0100
From:   Greg KH <gregkh@...uxfoundation.org>
To:     Gregory Price <gourry.memverge@...il.com>
Cc:     linux-kernel@...r.kernel.org, rafael@...nel.org,
        Gregory Price <gregory.price@...verge.com>
Subject: Re: [PATCH] base/node.c: initialize the accessor list before
 registering

On Mon, Oct 30, 2023 at 12:42:39AM -0400, Gregory Price wrote:
> The current code registers the node as available in the node array
> before initializing the accessor list.  This makes it so that
> anything which might access the accessor list as a result of
> allocations will cause an undefined memory access.
> 
> In one example, an extension to access hmat data during interleave
> caused this undefined access as a result of a bulk allocation
> that occurs during node initialization but before the accessor
> list is initialized.

Is this an in-kernel driver that causes this problem?

> 
> Initialize the accessor list before making the node generally
> available to the global system.
> 
> Signed-off-by: Gregory Price <gregory.price@...verge.com>

What commit id does this fix?

thanks,

greg k-h