linux-kernel - Re: KASAN: stack-out-of-bounds Write in end_buffer_read

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

Message-ID: <ZsQVwUVdR5jQOPFJ@casper.infradead.org>
Date: Tue, 20 Aug 2024 05:04:17 +0100
From: Matthew Wilcox <willy@...radead.org>
To: Aleksandr Nogikh <nogikh@...gle.com>
Cc: Hui Guo <guohui.study@...il.com>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Alexander Potapenko <glider@...gle.com>,
	Marco Elver <elver@...gle.com>, linux-kernel@...r.kernel.org,
	Mark Rutland <mark.rutland@....com>, Ingo Molnar <mingo@...nel.org>,
	"Peter Zijlstra (Intel)" <peterz@...radead.org>,
	"Paul E. McKenney" <paulmck@...nel.org>,
	Uros Bizjak <ubizjak@...il.com>,
	Carlos Llamas <cmllamas@...gle.com>, Jens Axboe <axboe@...nel.dk>,
	Pankaj Raghav <p.raghav@...sung.com>,
	Ryusuke Konishi <konishi.ryusuke@...il.com>,
	Al Viro <viro@...iv.linux.org.uk>,
	Christian Brauner <brauner@...nel.org>, Jan Kara <jack@...e.cz>,
	linux-fsdevel@...r.kernel.org, syzkaller-bugs@...glegroups.com
Subject: Re: KASAN: stack-out-of-bounds Write in end_buffer_read_sync

On Mon, Aug 19, 2024 at 03:28:13PM +0200, Aleksandr Nogikh wrote:
> On Mon, Aug 19, 2024 at 2:54 PM Hui Guo <guohui.study@...il.com> wrote:
> >
> > Hi Kernel Maintainers,
> > Our tool found the following kernel bug "KASAN: stack-out-of-bounds
> > Write in end_buffer_read_sync" on:
> 
> Please note that the bug was already reported by syzbot in 2022:
> https://syzkaller.appspot.com/bug?extid=3f7f291a3d327486073c
> https://lore.kernel.org/all/0000000000005b04fa05dd71e0e0@google.com/T/

Oh, syzbot was more useful than Hui Guo.  It pointed out that it's
an NTFS problem, so nobody cared.  I'll go back to not caring.