linux-kernel - Re: [syzbot] [hfs] general protection fault in tomoyo_check

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

Message-ID: <20240111092147.ywwuk4vopsml3plk@quack3>
Date: Thu, 11 Jan 2024 10:21:47 +0100
From: Jan Kara <jack@...e.cz>
To: syzbot <syzbot+28aaddd5a3221d7fd709@...kaller.appspotmail.com>
Cc: axboe@...nel.dk, brauner@...nel.org, jack@...e.cz, jmorris@...ei.org,
	linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org,
	linux-security-module@...r.kernel.org, paul@...l-moore.com,
	penguin-kernel@...ove.SAKURA.ne.jp, serge@...lyn.com,
	syzkaller-bugs@...glegroups.com, takedakn@...data.co.jp,
	tomoyo-dev-en-owner@...ts.osdn.me, tomoyo-dev-en@...ts.osdn.me
Subject: Re: [syzbot] [hfs] general protection fault in tomoyo_check_acl (3)

On Wed 10-01-24 22:44:04, syzbot wrote:
> syzbot suspects this issue was fixed by commit:
> 
> commit 6f861765464f43a71462d52026fbddfc858239a5
> Author: Jan Kara <jack@...e.cz>
> Date:   Wed Nov 1 17:43:10 2023 +0000
> 
>     fs: Block writes to mounted block devices
> 
> bisection log:  https://syzkaller.appspot.com/x/bisect.txt?x=15135c0be80000
> start commit:   a901a3568fd2 Merge tag 'iomap-6.5-merge-1' of git://git.ke..
> git tree:       upstream
> kernel config:  https://syzkaller.appspot.com/x/.config?x=7406f415f386e786
> dashboard link: https://syzkaller.appspot.com/bug?extid=28aaddd5a3221d7fd709
> syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=17b5bb80a80000
> C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=10193ee7280000
> 
> If the result looks correct, please mark the issue as fixed by replying with: 

Makes some sense since fs cannot be corrupted by anybody while it is
mounted. I just don't see how the reproducer would be corrupting the
image... Still probably:

#syz fix: fs: Block writes to mounted block devices

and we'll see if syzbot can find new ways to tickle some similar problem.

								Honza
-- 
Jan Kara <jack@...e.com>
SUSE Labs, CR