linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: syzbot <syzbot+29934710e7fb9cb71f33@syzkaller.appspotmail.com>
To: aha310510@gmail.com, eadavis@qq.com, ethan.ferguson@zetier.com,
	 linkinjeon@kernel.org, linux-fsdevel@vger.kernel.org,
	 linux-kernel@vger.kernel.org, sj1557.seo@samsung.com,
	 syzkaller-bugs@googlegroups.com, yuezhang.mo@sony.com
Subject: Re: [syzbot] [exfat?] KASAN: stack-out-of-bounds Read in exfat_nls_to_ucs2
Date: Sun, 16 Nov 2025 03:46:03 -0800	[thread overview]
Message-ID: <6919b97b.a70a0220.3124cb.007c.GAE@google.com> (raw)
In-Reply-To: <68ed75c7.050a0220.91a22.01ee.GAE@google.com>

syzbot suspects this issue was fixed by commit:

commit 2d8636119b92970ba135c3c4da87d24dbfdeb8ca
Author: Jeongjun Park <aha310510@gmail.com>
Date:   Wed Oct 15 07:34:54 2025 +0000

    exfat: fix out-of-bounds in exfat_nls_to_ucs2()

bisection log:  https://syzkaller.appspot.com/x/bisect.txt?x=17f5a212580000
start commit:   67029a49db6c Merge tag 'trace-v6.18-3' of git://git.kernel..
git tree:       upstream
kernel config:  https://syzkaller.appspot.com/x/.config?x=1921939e847e6e87
dashboard link: https://syzkaller.appspot.com/bug?extid=29934710e7fb9cb71f33
syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=11aa067c580000
C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=12ba29e2580000

If the result looks correct, please mark the issue as fixed by replying with:

#syz fix: exfat: fix out-of-bounds in exfat_nls_to_ucs2()

For information about bisection process see: https://goo.gl/tpsmEJ#bisection

      parent reply	other threads:[~2025-11-16 11:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-13 21:57 [syzbot] [exfat?] KASAN: stack-out-of-bounds Read in exfat_nls_to_ucs2 syzbot
2025-10-14  4:39 ` [PATCH] exfat: Use str length when converting to utf16 Edward Adam Davis
2025-11-16 11:46 ` syzbot [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=6919b97b.a70a0220.3124cb.007c.GAE@google.com \
    --to=syzbot+29934710e7fb9cb71f33@syzkaller.appspotmail.com \
    --cc=aha310510@gmail.com \
    --cc=eadavis@qq.com \
    --cc=ethan.ferguson@zetier.com \
    --cc=linkinjeon@kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sj1557.seo@samsung.com \
    --cc=syzkaller-bugs@googlegroups.com \
    --cc=yuezhang.mo@sony.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).