From: Hongbo Li <lihongbo22@huawei.com>
To: Gao Xiang <hsiangkao@linux.alibaba.com>, <linux-erofs@lists.ozlabs.org>
Cc: LKML <linux-kernel@vger.kernel.org>, Robert Morris <rtm@mit.edu>,
Robert Morris <rtm@csail.mit.edu>
Subject: Re: [PATCH v2] erofs: fix crafted invalid cases for encoded extents
Date: Mon, 13 Oct 2025 12:16:33 +0800 [thread overview]
Message-ID: <62036acc-04f3-4dec-98c9-343def13d3c4@huawei.com> (raw)
In-Reply-To: <20251012135925.158921-1-hsiangkao@linux.alibaba.com>
On 2025/10/12 21:59, Gao Xiang wrote:
> Robert recently reported two corrupted images that can cause system
> crashes, which are related to the new encoded extents introduced
> in Linux 6.15:
>
> - The first one [1] has plen != 0 (e.g. plen == 0x2000000) but
> (plen & Z_EROFS_EXTENT_PLEN_MASK) == 0. It is used to represent
> special extents such as sparse extents (!EROFS_MAP_MAPPED), but
> previously only plen == 0 was handled;
>
> - The second one [2] has pa 0xffffffffffdcffed and plen 0xb4000,
> then "cur [0xfffffffffffff000] += bvec.bv_len [0x1000]" in
> "} while ((cur += bvec.bv_len) < end);" wraps around, causing an
> out-of-bound access of pcl->compressed_bvecs[] in
> z_erofs_submit_queue(). EROFS only supports 48-bit physical block
> addresses (up to 1EiB for 4k blocks), so add a sanity check to
> enforce this.
>
> Fixes: 1d191b4ca51d ("erofs: implement encoded extent metadata")
> Reported-by: Robert Morris <rtm@csail.mit.edu>
> Closes: https://lore.kernel.org/r/75022.1759355830@localhost
> Closes: https://lore.kernel.org/r/80524.1760131149@localhost
> Signed-off-by: Gao Xiang <hsiangkao@linux.alibaba.com>
Reviewed-by: Hongbo Li <lihongbo22@huawei.com>
Thanks,
Hongbo
> ---
> v2:
> - `pend` should be converted to blocks and then be compared.
>
> fs/erofs/zmap.c | 7 ++++++-
> 1 file changed, 6 insertions(+), 1 deletion(-)
>
> diff --git a/fs/erofs/zmap.c b/fs/erofs/zmap.c
> index 798223e6da9c..87032f90fe84 100644
> --- a/fs/erofs/zmap.c
> +++ b/fs/erofs/zmap.c
> @@ -596,7 +596,7 @@ static int z_erofs_map_blocks_ext(struct inode *inode,
> vi->z_fragmentoff = map->m_plen;
> if (recsz > offsetof(struct z_erofs_extent, pstart_lo))
> vi->z_fragmentoff |= map->m_pa << 32;
> - } else if (map->m_plen) {
> + } else if (map->m_plen & Z_EROFS_EXTENT_PLEN_MASK) {
> map->m_flags |= EROFS_MAP_MAPPED |
> EROFS_MAP_FULL_MAPPED | EROFS_MAP_ENCODED;
> fmt = map->m_plen >> Z_EROFS_EXTENT_PLEN_FMT_BIT;
> @@ -715,6 +715,7 @@ static int z_erofs_map_sanity_check(struct inode *inode,
> struct erofs_map_blocks *map)
> {
> struct erofs_sb_info *sbi = EROFS_I_SB(inode);
> + u64 pend;
>
> if (!(map->m_flags & EROFS_MAP_ENCODED))
> return 0;
> @@ -732,6 +733,10 @@ static int z_erofs_map_sanity_check(struct inode *inode,
> if (unlikely(map->m_plen > Z_EROFS_PCLUSTER_MAX_SIZE ||
> map->m_llen > Z_EROFS_PCLUSTER_MAX_DSIZE))
> return -EOPNOTSUPP;
> + /* Filesystems beyond 48-bit physical block addresses are invalid */
> + if (unlikely(check_add_overflow(map->m_pa, map->m_plen, &pend) ||
> + (pend >> sbi->blkszbits) >= BIT_ULL(48)))
> + return -EFSCORRUPTED;
> return 0;
> }
>
prev parent reply other threads:[~2025-10-13 4:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <2cda3cc5-f837-4627-9587-051ed10839b9@linux.alibaba.com>
2025-10-12 13:59 ` Gao Xiang
2025-10-13 4:16 ` Hongbo Li [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=62036acc-04f3-4dec-98c9-343def13d3c4@huawei.com \
--to=lihongbo22@huawei.com \
--cc=hsiangkao@linux.alibaba.com \
--cc=linux-erofs@lists.ozlabs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rtm@csail.mit.edu \
--cc=rtm@mit.edu \
/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
all inboxes | Powered by JetHome®