linux-kernel - Re: [git pull] coredump infoleak fix

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: <20200529093911.GF790247@gmail.com>
Date:   Fri, 29 May 2020 11:39:11 +0200
From:   Ingo Molnar <mingo@...nel.org>
To:     Al Viro <viro@...iv.linux.org.uk>
Cc:     Linus Torvalds <torvalds@...ux-foundation.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        the arch/x86 maintainers <x86@...nel.org>
Subject: Re: [git pull] coredump infoleak fix


* Al Viro <viro@...iv.linux.org.uk> wrote:

> On Thu, May 28, 2020 at 11:34:38AM -0700, Linus Torvalds wrote:
> > On Thu, May 28, 2020 at 12:03 AM Ingo Molnar <mingo@...nel.org> wrote:
> > >
> > > I'm wondering, shouldn't we also zero-initialize the dump data to
> > > begin with? See the patch below (untested).
> > 
> > I actually got this patch from Andrew today independently due to a
> > KMSAN report. Which I'm applying.
> 
> It doesn't fix all problems, though - you don't get an infoleak, but
> you do get incorrect data...

BTW., I pulled this into x86/urgent with a potential v5.7 merge, 
although it's getting tight.

I think the ptrace impact qualifies it for v5.7?

Thanks,

	Ingo