From: Jeongjun Park <aha310510@gmail.com>
To: willy@infradead.org
Cc: brauner@kernel.org, eadavis@qq.com,
jfs-discussion@lists.sourceforge.net, jlayton@kernel.org,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
shaggy@kernel.org,
syzbot+241c815bda521982cb49@syzkaller.appspotmail.com,
syzkaller-bugs@googlegroups.com
Subject: Re: [PATCH] jfs: Fix array-index-out-of-bounds in diFree
Date: Thu, 25 Apr 2024 21:44:33 +0900 [thread overview]
Message-ID: <20240425124433.28645-1-aha310510@gmail.com> (raw)
In-Reply-To: <ZilEXC3qLiqMTs29@casper.infradead.org>
Through direct testing and debugging, I've determined that this
vulnerability occurs when mounting an incorrect image, leading to
the potential passing of an excessively large value to
'sbi->bmap->db_agl2size'. Importantly, there have been no instances
of memory corruption observed within 'sbi->bmap->db_agl2size'.
Therefore, I think implementing a patch that terminates the
function in cases where an invalid value is detected.
Thanks.
next prev parent reply other threads:[~2024-04-25 12:44 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-23 22:25 [syzbot] [jfs?] UBSAN: array-index-out-of-bounds in diFree syzbot
2024-04-24 17:22 ` [PATCH] jfs: Fix " Jeongjun Park
2024-04-24 17:41 ` Matthew Wilcox
2024-04-25 12:44 ` Jeongjun Park [this message]
2024-04-25 12:53 ` Matthew Wilcox
2024-04-25 14:10 ` Jeongjun Park
2024-04-25 14:14 ` Dave Kleikamp
2024-04-25 14:17 ` Matthew Wilcox
2024-04-25 14:24 ` Jeongjun Park
2024-04-25 17:04 ` Matthew Wilcox
2024-04-26 1:42 ` Jeongjun Park
2024-04-26 2:34 ` Jeongjun Park
2024-04-26 3:27 ` Matthew Wilcox
2024-04-26 3:41 ` Jeongjun Park
2024-05-30 13:28 ` Jeongjun Park
2024-06-26 17:40 ` Dave Kleikamp
2024-04-25 14:24 ` Dave Kleikamp
2024-04-25 14:37 ` Jeongjun Park
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=20240425124433.28645-1-aha310510@gmail.com \
--to=aha310510@gmail.com \
--cc=brauner@kernel.org \
--cc=eadavis@qq.com \
--cc=jfs-discussion@lists.sourceforge.net \
--cc=jlayton@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=shaggy@kernel.org \
--cc=syzbot+241c815bda521982cb49@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=willy@infradead.org \
/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).