linux-kernel - Re: [PATCH] x86/nmi/64: avoid passing user space rsp of pt

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <39192236-BD33-47C1-AB14-F2FE2FF74566@amacapital.net>
Date:   Wed, 23 Aug 2017 09:51:01 -0700
From:   Andy Lutomirski <luto@...capital.net>
To:     Josh Poimboeuf <jpoimboe@...hat.com>
Cc:     oliver yang <yangoliver@...il.com>,
        yang oliver <yang_oliver@...mail.com>,
        "tglx@...utronix.de" <tglx@...utronix.de>,
        "mingo@...hat.com" <mingo@...hat.com>,
        "hpa@...or.com" <hpa@...or.com>,
        "luto@...nel.org" <luto@...nel.org>,
        "x86@...nel.org" <x86@...nel.org>,
        "rostedt@...dmis.org" <rostedt@...dmis.org>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] x86/nmi/64: avoid passing user space rsp of pt_regs to nmi handler

To avoid further wasting time solving this wrong: NAK.  pt_regs is the actual interrupted state, not some oddly sanitized version thereof.  NMI isn't even the only way you can have a weird pt_regs like this.

It seems that some older kernels contain bugs where they incorrectly assume that regs->rsp is a valid pointer.  Why don't you write a patch for *that * and send it to lkml, us, and stable@...r.kernel.org.