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  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]
Date:   Tue, 26 Mar 2019 10:41:23 -0700
From:   Matthew Garrett <>
To:     Masami Hiramatsu <>
Cc:     James Morris <>,
        LSM List <>,
        Linux Kernel Mailing List <>,
        David Howells <>,
        Alexei Starovoitov <>,
        "Naveen N . Rao" <>,
        Anil S Keshavamurthy <>,
Subject: Re: [PATCH 22/27] Lock down kprobes

On Tue, Mar 26, 2019 at 5:30 AM Masami Hiramatsu <> wrote:
> On Mon, 25 Mar 2019 15:09:49 -0700
> Matthew Garrett <> wrote:
> > From: David Howells <>
> >
> > Disallow the creation of kprobes when the kernel is locked down by
> > preventing their registration.  This prevents kprobes from being used to
> > access kernel memory, either to make modifications or to steal crypto data.
> Hmm, if you enforce signature check of modules, those modules
> should be allowed to use kprobes?
> I think we should introduce some kind of trust inheritance from
> signed (trusted) modules.

Is there any way to install a kprobe /without/ it coming from a
module? The presumption in lockdown mode is that module signing is
enforced, so I'll admit to not being entirely clear on why this patch
is needed in that case.

Powered by blists - more mailing lists