Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::3:1 as permitted sender) client-ip=2620:137:e000::3:1;
From:   Dan Moulding <dan@danm.net>
To:     sam@gentoo.org
Cc:     dan@danm.net, linux-hardening@vger.kernel.org,
        linux-kernel@vger.kernel.org, stable@vger.kernel.org,
        toralf.foerster@gmx.de
Subject: Re: 6.5.13 regression: BUG: kernel NULL pointer dereference, address: 0000000000000020
Date:   Tue, 28 Nov 2023 15:48:16 -0700
Message-ID: <20231128224816.6563-1-dan@danm.net>
In-Reply-To: <87jzq1lflc.fsf@gentoo.org>
References: <87jzq1lflc.fsf@gentoo.org>
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Precedence: bulk

Thanks, Sam. Yes it does look like that's the same issue.

I applied that patch to v6.6.3 instead of reverting the change to the
randomize_layout plugin and the problem also goes away with the patch
applied.

In that thread with the patch, Gustavo does mention that many other
zero-length arrays, besides this one in struct neighbor, were found in
the kernel source. But a quick (and possibly imperfect) grepping seems
to show that struct neighbor was the only one used with
__randomize_layout. So, I *think* it might be the only one that could
cause a problem with the recent change to the randomize_layout plugin.

-- Dan