linux-kernel - RE: [tip: x86/core] objtool: Find unused ENDBR instructions

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: <a5fa50d9f00542de8a6ad7a3fe0c49b3@AcuMS.aculab.com>
Date:   Tue, 15 Mar 2022 15:39:52 +0000
From:   David Laight <David.Laight@...LAB.COM>
To:     "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        "linux-tip-commits@...r.kernel.org" 
        <linux-tip-commits@...r.kernel.org>
CC:     "Peter Zijlstra (Intel)" <peterz@...radead.org>,
        Josh Poimboeuf <jpoimboe@...hat.com>,
        "x86@...nel.org" <x86@...nel.org>
Subject: RE: [tip: x86/core] objtool: Find unused ENDBR instructions

From: Peter Zijlstra
> 
> objtool: Find unused ENDBR instructions
> 
> Find all ENDBR instructions which are never referenced and stick them
> in a section such that the kernel can poison them, sealing the
> functions from ever being an indirect call target.

Thought, what happens if the only indirect call is from
code in a module?

	David

-
Registered Address Lakeside, Bramley Road, Mount Farm, Milton Keynes, MK1 1PT, UK
Registration No: 1397386 (Wales)