From: Dave Kleikamp <dave.kleikamp@oracle.com>
To: Siddh Raman Pant <code@siddh.me>,
Dongliang Mu <mudongliangabcd@gmail.com>,
Liu Shixin <liushixin2@huawei.com>,
Hoi Pok Wu <wuhoipok@gmail.com>
Cc: jfs-discussion@lists.sourceforge.net,
linux-kernel@vger.kernel.org,
Anup Sharma <anupnewsmail@gmail.com>,
syzbot+d2cd27dcf8e04b232eb2@syzkaller.appspotmail.com,
stable@vger.kernel.org
Subject: Re: [PATCH] jfs: jfs_dmap: Validate db_l2nbperpage while mounting
Date: Fri, 16 Jun 2023 17:16:09 -0500 [thread overview]
Message-ID: <6284256f-dacc-e287-fe07-377491f87ca3@oracle.com> (raw)
In-Reply-To: <20230605140151.635604-1-code@siddh.me>
On 6/5/23 9:01AM, Siddh Raman Pant wrote:
> In jfs_dmap.c at line 381, BLKTODMAP is used to get a logical block
> number inside dbFree(). db_l2nbperpage, which is the log2 number of
> blocks per page, is passed as an argument to BLKTODMAP which uses it
> for shifting.
>
> Syzbot reported a shift out-of-bounds crash because db_l2nbperpage is
> too big. This happens because the large value is set without any
> validation in dbMount() at line 181.
>
> Thus, make sure that db_l2nbperpage is correct while mounting.
>
> Reported-and-tested-by: syzbot+d2cd27dcf8e04b232eb2@syzkaller.appspotmail.com
> Link: https://syzkaller.appspot.com/bug?id=2a70a453331db32ed491f5cbb07e81bf2d225715
> Cc: stable@vger.kernel.org
> Signed-off-by: Siddh Raman Pant <code@siddh.me>
> ---
> fs/jfs/jfs_dmap.c | 6 ++++++
> 1 file changed, 6 insertions(+)
>
> diff --git a/fs/jfs/jfs_dmap.c b/fs/jfs/jfs_dmap.c
> index a3eb1e826947..62f058822a3a 100644
> --- a/fs/jfs/jfs_dmap.c
> +++ b/fs/jfs/jfs_dmap.c
> @@ -178,7 +178,13 @@ int dbMount(struct inode *ipbmap)
> dbmp_le = (struct dbmap_disk *) mp->data;
> bmp->db_mapsize = le64_to_cpu(dbmp_le->dn_mapsize);
> bmp->db_nfree = le64_to_cpu(dbmp_le->dn_nfree);
> +
> bmp->db_l2nbperpage = le32_to_cpu(dbmp_le->dn_l2nbperpage);
> + if (bmp->db_l2nbperpage > L2MAXL0SIZE) {
Actually the sanity check should be much smaller. The maximum value
should be L2PSIZE - log2(MINBLOCKSIZE). In reality, I think it's always
zero.
Shaggy
> + err = -EINVAL;
> + goto err_release_metapage;
> + }
> +
> bmp->db_numag = le32_to_cpu(dbmp_le->dn_numag);
> if (!bmp->db_numag) {
> err = -EINVAL;
next prev parent reply other threads:[~2023-06-16 23:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-05 14:01 [PATCH] jfs: jfs_dmap: Validate db_l2nbperpage while mounting Siddh Raman Pant
2023-06-16 22:16 ` Dave Kleikamp [this message]
2023-06-19 12:02 ` Siddh Raman Pant
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=6284256f-dacc-e287-fe07-377491f87ca3@oracle.com \
--to=dave.kleikamp@oracle.com \
--cc=anupnewsmail@gmail.com \
--cc=code@siddh.me \
--cc=jfs-discussion@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=liushixin2@huawei.com \
--cc=mudongliangabcd@gmail.com \
--cc=stable@vger.kernel.org \
--cc=syzbot+d2cd27dcf8e04b232eb2@syzkaller.appspotmail.com \
--cc=wuhoipok@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.