linux-kernel - Re: [PATCH v2 RESEND] x86/kaslr: Ingest nokaslr to avoid passing it to init process

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: <20250114203024.GEZ4bJYCKMx2VOWCcz@fat_crate.local>
Date: Tue, 14 Jan 2025 21:30:24 +0100
From: Borislav Petkov <bp@...en8.de>
To: Nir Lichtman <nir_lichtman@...mail.com>
Cc: Peter Zijlstra <peterz@...radead.org>,
	"dave.hansen@...ux.intel.com" <dave.hansen@...ux.intel.com>,
	"luto@...nel.org" <luto@...nel.org>,
	"tglx@...utronix.de" <tglx@...utronix.de>,
	"mingo@...hat.com" <mingo@...hat.com>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"m.younesbadr@...il.com" <m.younesbadr@...il.com>,
	Nir Lichtman <nir@...htman.org>
Subject: Re: [PATCH v2 RESEND] x86/kaslr: Ingest nokaslr to avoid passing it
 to init process

On Tue, Jan 14, 2025 at 03:02:34PM +0000, Nir Lichtman wrote:
> Yes indeed, when I made an initramfs with cpio and put a static bash build
> as ./init, It got the nokaslr as the first argument and crashed, this causes
> a general panic since the init process crashed.
> 
> This behavior of passing unrecognized params to the init process is
> documented in the kernel docs, and also in the corresponding warning
> message.

So you must be doing something special because all of our systems are running
fine with "nokaslr". As said, stuff would be breaking left'n'right if this
were really a problem.

-- 
Regards/Gruss,
    Boris.

https://people.kernel.org/tglx/notes-about-netiquette