linux-kernel - Re: [RFC v1 0/3] Address potential user-after-free on module unload

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]

Date:   Tue, 5 Feb 2019 19:42:50 +0100
From:   Greg KH <gregkh@...uxfoundation.org>
To:     Kees Cook <keescook@...omium.org>
Cc:     Sven Van Asbroeck <thesven73@...il.com>, Tejun Heo <tj@...nel.org>,
        Lai Jiangshan <jiangshanlai@...il.com>,
        LKML <linux-kernel@...r.kernel.org>,
        Sebastian Reichel <sre@...nel.org>,
        Dmitry Torokhov <dmitry.torokhov@...il.com>
Subject: Re: [RFC v1 0/3] Address potential user-after-free on module unload

On Tue, Feb 05, 2019 at 02:57:11PM +0000, Kees Cook wrote:
> On Mon, Feb 4, 2019 at 10:09 PM Sven Van Asbroeck <thesven73@...il.com> wrote:
> >
> > I think there _might_ be potential use-after-free issues on module unload.

There are loads of issues with module unloading, which is why it pretty
much is a "best effort" type of thing.  It never happens automatically
and the only way you can do it is if you have root access, at which
point, there are loads of other things you can do that are much worse :)

thanks,

greg k-h