linux-kernel - Re: [syzbot] kernel stack overflow in sock

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>] [day] [month] [year] [list]

Message-ID: <Y5ND9qNFXOxOuEMQ@FVFF77S0Q05N>
Date:   Fri, 9 Dec 2022 14:19:34 +0000
From:   Mark Rutland <mark.rutland@....com>
To:     Hillf Danton <hdanton@...a.com>
Cc:     syzbot <syzbot+09329bd987ebca21bced@...kaller.appspotmail.com>,
        john.fastabend@...il.com, linux-kernel@...r.kernel.org,
        netdev@...r.kernel.org, syzkaller-bugs@...glegroups.com,
        Robin Murphy <robin.murphy@....com>
Subject: Re: [syzbot] kernel stack overflow in sock_close

On Fri, Dec 09, 2022 at 09:32:14PM +0800, Hillf Danton wrote:
> On 9 Dec 2022 13:15:39 +0000 Mark Rutland <mark.rutland@....com>
> > On Thu, Dec 08, 2022 at 02:05:36AM -0800, syzbot wrote:
> > > Hello,
> > > 
> > > syzbot found the following issue on:
> > > 
> > > HEAD commit:    e3cb714fb489 Merge branch 'for-next/core' into for-kernelci
> > 
> > This commit has a known-broken parent where some uaccess copies appeared to
> > result in stack corruption:
> > 
> >   https://lore.kernel.org/linux-arm-kernel/Y44gVm7IEMXqilef@FVFF77S0Q05N.cambridge.arm.com/
> > 
> > ... which has now been dropped from the arm64 for-next/core branch, but
> > anything found on commit e3cb714fb489 will be suspect due to that.
> > 
> > This *might* a manifestation of the same issue; I'll have a go at reproducing
> > it locally.
> 
> Take a look at the reproducer [1] before kicking off your Harley.
> 
> [1] https://lore.kernel.org/lkml/00000000000073b14905ef2e7401@google.com/

Ah, yes; this is clearly not arm64-specific, and therefore has
nothing to do with the uaccess issue.

Sorry for the noise, and thanks for the pointer!

Mark.