[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <YpyNWgSXNityT14C@zeniv-ca.linux.org.uk>
Date: Sun, 5 Jun 2022 11:02:50 +0000
From: Al Viro <viro@...iv.linux.org.uk>
To: syzbot <syzbot+47dd250f527cb7bebf24@...kaller.appspotmail.com>
Cc: linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org,
syzkaller-bugs@...glegroups.com
Subject: Re: [syzbot] KASAN: use-after-free Read in filp_close
On Sun, Jun 05, 2022 at 01:49:19AM -0700, syzbot wrote:
> syzbot has found a reproducer for the following issue on:
>
> HEAD commit: 952923ddc011 Merge tag 'pull-18-rc1-work.namei' of git://g..
> git tree: upstream
> console output: https://syzkaller.appspot.com/x/log.txt?x=173fb6dbf00000
> kernel config: https://syzkaller.appspot.com/x/.config?x=3096247591885bfa
> dashboard link: https://syzkaller.appspot.com/bug?extid=47dd250f527cb7bebf24
> compiler: gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2
> syz repro: https://syzkaller.appspot.com/x/repro.syz?x=114f7bcdf00000
> C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1659a94ff00000
_Very_ interesting. Has anything of that sort been observed on -next?
Because everything in that branch had been present there since at least
January.
Powered by blists - more mailing lists