linux-kernel - Re: [PATCH] x86/module: Fixed bug allowing invalid relocation addresses.

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>] [day] [month] [year] [list]

Message-ID: <20200318195803.GE4377@zn.tnic>
Date:   Wed, 18 Mar 2020 20:58:04 +0100
From:   Borislav Petkov <bp@...en8.de>
To:     gilad kleinman <dkgs1998@...il.com>
Cc:     Peter Zijlstra <peterz@...radead.org>,
        Thomas Gleixner <tglx@...utronix.de>,
        Ingo Molnar <mingo@...hat.com>,
        "H. Peter Anvin" <hpa@...or.com>, x86@...nel.org,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH] x86/module: Fixed bug allowing invalid relocation
 addresses.

On Wed, Mar 18, 2020 at 09:40:47PM +0200, gilad kleinman wrote:
> When you load a bad module and the kernel crashes -- the panic message will
> usually be related to the module and easily traced back. If you load a
> module with a bad relocation table (because of a bit-flip \ bad toolchain),

First of all, please do not top-post.

Then, if you're worried about corrupted module text, we have
CONFIG_MODULE_SIG which verifies previously signed modules. AFAICT, that
should take care of the issue you're talking about here.

Thx.

-- 
Regards/Gruss,
    Boris.

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