linux-kernel - Re: [syzbot] [udf?] general protection fault in udf_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: <20241022090222.tndd3zqlgtohjnce@quack3>
Date: Tue, 22 Oct 2024 11:02:22 +0200
From: Jan Kara <jack@...e.cz>
To: Gianfranco Trad <gianf.trad@...il.com>
Cc: jan Kara <jack@...e.com>,
	syzbot <syzbot+ddf8715339c89280b6fc@...kaller.appspotmail.com>,
	linux-kernel@...r.kernel.org
Subject: Re: [syzbot] [udf?] general protection fault in udf_read_folio

On Tue 22-10-24 02:19:19, Gianfranco Trad wrote:
> On 22/10/24 02:04, syzbot wrote:
> > Hello,
> > 
> > syzbot has tested the proposed patch and the reproducer did not trigger any issue:
> > 
> > Reported-by: syzbot+ddf8715339c89280b6fc@...kaller.appspotmail.com
> > Tested-by: syzbot+ddf8715339c89280b6fc@...kaller.appspotmail.com
> > 
> > Tested on:
> > 
> > commit:         c2ee9f59 KVM: selftests: Fix build on on non-x86 archi..
> > git tree:       upstream
> > console output: https://syzkaller.appspot.com/x/log.txt?x=12684640580000
> > kernel config:  https://syzkaller.appspot.com/x/.config?x=fc6f8ce8c5369043
> > dashboard link: https://syzkaller.appspot.com/bug?extid=ddf8715339c89280b6fc
> > compiler:       Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
> > 
> > Note: no patches were applied.
> > Note: testing is done by a robot and is best-effort only.
> 
> Hi Jan,
> 
> syzbot reported a null-ptr-deref in udf_read_folio a month ago [1].
> 
> This bug was marked as still open on syzbot, so I retested the reproducer
> (no patch applied) to check if the bug was still valid upstream, seems not
> (as reported up).
> Wondering if syzbot will now try to find another reproducer, since after
> this check the reproducer was crossed away on the syzbot web UI, or if the
> bug can be considered closed.
> I hope this might help.

I believe syzbot tries to bisect back to the fix and reports it. Then
either you can ack it (which closes the bug) or the bug will auto-close
after some time if there's no reproducer.

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