[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20240426014241.51894-1-aha310510@gmail.com>
Date: Fri, 26 Apr 2024 10:42:41 +0900
From: Jeongjun Park <aha310510@...il.com>
To: willy@...radead.org
Cc: brauner@...nel.org,
jfs-discussion@...ts.sourceforge.net,
jlayton@...nel.org,
linux-fsdevel@...r.kernel.org,
linux-kernel@...r.kernel.org,
shaggy@...nel.org,
syzbot+241c815bda521982cb49@...kaller.appspotmail.com,
syzkaller-bugs@...glegroups.com
Subject: Re: [PATCH] jfs: Fix array-index-out-of-bounds in diFree
Matthew Wilcox wrote:
> In your earlier mail, you said the large value was found in db_agl2size.
> If the problem is in agstart then diRead() is the right place to check it.
Oh, I was so distracted last time that I wrote the explanation
incorrectly. I'm sorry.
To explain it accurately, if you pass a very large value to agstart
and set the value passed to db_agl2size to be small, it can be
manipulated so that a value greater than MAXAG is output when the
"agstart >> db_agl2size" operation is performed.
This results in an out-of-bounds vulnerability.
And the final patch before is the one that fixes diRead().
Thanks.
Powered by blists - more mailing lists