linux-kernel - Re: BUG: kernel NULL pointer dereference, address: 0000000000000000

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <8f8a478ba50bd43d30704f0d74e02058810f2795.camel@debian.org>
Date: Tue, 27 Jan 2026 08:01:43 +0100
From: Giuseppe Sacco <eppesuig@...ian.org>
To: Sudip Mukherjee <sudipm.mukherjee@...il.com>, Salvatore Bonaccorso
	 <carnil@...ian.org>
Cc: Paul Menzel <pmenzel@...gen.mpg.de>, Sudip Mukherjee	
 <sudip.mukherjee@...ethink.co.uk>, linux-kernel@...r.kernel.org, Andrew
 Morton	 <akpm@...ux-foundation.org>, linux-mm@...ck.org,
 regressions@...ts.linux.dev,  Thomas Gleixner <tglx@...utronix.de>, Ingo
 Molnar <mingo@...hat.com>, Borislav Petkov <bp@...en8.de>, Dave Hansen	
 <dave.hansen@...ux.intel.com>, x86@...nel.org, Hans de Goede
 <hansg@...nel.org>,  Ilpo Järvinen	
 <ilpo.jarvinen@...ux.intel.com>
Subject: Re: BUG: kernel NULL pointer dereference, address: 0000000000000000

Hello Sudip,

Il giorno lun, 26/01/2026 alle 18.56 +0000, Sudip Mukherjee ha scritto:
[...]
> I was going to post the patch today but since you have asked the
> reporter of the last bug to test it so lets wait for few more days.
> 
> About the problem showing on the first boot, does that mean that its
> only seen on a cold boot ? and not seen on reboots (reboots without
> power cycle) ?
> Can it be reproduced if the system is powered-off and then powering
> it on ?

I am that reporter. The problem appeared only once, on a laptop that is
never just rebooted, i.e., it is always completely powered off and
started again after a few hours. I've built the kernel with your patch
but I would not use it until I would find a way to reproduce the error.
Sadly I was unable to see the problem again.

The only hint I may provide is that the day the problem showed up, I
was working in the wild, at about 10°C. Maybe this has influenced the
hardware response timeing.

Bye,
Giuseppe