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:   Fri, 12 May 2017 12:08:57 -0700
From:   Linus Torvalds <>
To:     Kees Cook <>
Cc:     Martin Schwidefsky <>,
        Thomas Garnier <>, Greg KH <>,
        Ingo Molnar <>,
        Daniel Micay <>,
        Heiko Carstens <>,
        Dave Hansen <>,
        Arnd Bergmann <>,
        Thomas Gleixner <>,
        David Howells <>,
        René Nyffenegger <>,
        Andrew Morton <>,
        "Paul E . McKenney" <>,
        "Eric W . Biederman" <>,
        Oleg Nesterov <>,
        Pavel Tikhomirov <>,
        Ingo Molnar <>,
        "H . Peter Anvin" <>,
        Andy Lutomirski <>,
        Paolo Bonzini <>,
        Rik van Riel <>,
        Josh Poimboeuf <>,
        Borislav Petkov <>,
        Brian Gerst <>,
        "Kirill A . Shutemov" <>,
        Christian Borntraeger <>,
        Russell King <>,
        Will Deacon <>,
        Catalin Marinas <>,
        Mark Rutland <>,
        James Morse <>,
        linux-s390 <>,
        LKML <>,
        Linux API <>,
        "the arch/x86 maintainers" <>,
        Kernel Hardening <>,
        Peter Zijlstra <>,
        Al Viro <>
Subject: Re: [kernel-hardening] Re: [PATCH v9 1/4] syscalls: Verify address
 limit before returning to user-mode

On Fri, May 12, 2017 at 12:01 PM, Kees Cook <> wrote:
> Yeah, the risk for "corrupted addr_limit" is mainly a concern for
> archs with addr_limit on the kernel stack. If I'm reading things
> correctly, that means, from the archs I've been paying closer
> attention to, it's an issue for arm, mips, and powerpc:

I don't understand why people are looking at addr_limit as some kind
of special thing.

If somebody is smashing the stack and corrupting thread info data, the
game is over. addr_limit is the *least* of your problems, and it's not
even all that likely that it will be increasing (it's much more likely
that it would be overwritten with a smaller value).

Quite frankly, this kind of idiotic discussion just makes me question
the whole idea of the patch.

Any "security" that is this specific is not real security, it's just
masturbatory garbage.

It may be worth checking that people use "set_fs()" properly. But stop
this idiotic crap. It just makes the kernel security people look like
the crazies.

There are enough incompetent crazy security people, don't go there.
The kinds of things it is worth protecting against are the big class
of generic issues, not the kind of "oh, but imagine if a cosmic ray
flips this particular word in memory" kind of crap that ignores all
the other words of memory.

Seriously, Kees. You are just making security people look bad. Stop it.


Powered by blists - more mailing lists