From: liubaolin <liubaolin12138@163.com>
To: Zhan Xusheng <zhanxusheng1024@gmail.com>,
Namjae Jeon <linkinjeon@kernel.org>,
Hyunchul Lee <hyc.lee@gmail.com>
Cc: Bryam Vargas <hexlabsecurity@proton.me>,
ntfs@lists.linux.dev, linux-kernel@vger.kernel.org,
Zhan Xusheng <zhanxusheng@xiaomi.com>
Subject: Re: [PATCH] ntfs: fix u16 truncation of the update sequence array count check
Date: Wed, 21 Oct 2026 09:16:41 +0800 [thread overview]
Message-ID: <754bcba2-2f8c-4bf5-8b12-16db8f485645@163.com> (raw)
In-Reply-To: <20261020134433.1015126-1-zhanxusheng1024@gmail.com>
在 2026/10/20 21:44, Zhan Xusheng 写道:
> From: Zhan Xusheng <zhanxusheng@xiaomi.com>
>
> ntfs_check_restart_page_header() bounds the on-disk system page size by
> recomputing the update sequence array count from it:
>
> u16 ra_ofs, usa_count, usa_ofs, usa_end = 0;
> ...
> usa_count = 1 + (logfile_system_page_size >> NTFS_BLOCK_SIZE_BITS);
> if (usa_count != le16_to_cpu(rp->usa_count))
> return false;
>
> The right hand side is computed in u32 but stored in a u16, so the count
> wraps once the system page size reaches 0x2000000. An image claiming any
> larger power of two passes the check by also claiming usa_count == 1.
>
> Nothing else limits the value, so ntfs_check_and_load_restart_page() goes
> on to kvzalloc() up to 2 GiB for the restart page and copy that many bytes
> a page at a time. The size is only rejected afterwards, by the
> (size >> NTFS_BLOCK_SIZE_BITS) != usa_count test in post_read_mst_fixup().
>
> Compute the count in a u32 so the existing check rejects an over-large
> system page size instead of being defeated by the truncation. This adds
> no new limit: the array holds one u16 per protected sector plus the update
> sequence number and must end within the first sector, which caps usa_count
> at 240 and the system page size at 64 KiB.
>
> Widen ra_ofs and usa_ofs as well, as ntfs_check_restart_area() already
> does: both are loaded from __le16 on-disk fields and every comparison is
> against a non-negative value, so no result changes.
>
> Fixes: 1e9ea7e04472 ("Revert "fs: Remove NTFS classic"")
> Signed-off-by: Zhan Xusheng <zhanxusheng@xiaomi.com>
> ---
> fs/ntfs/logfile.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/fs/ntfs/logfile.c b/fs/ntfs/logfile.c
> index ce38ce87f8fc8..2f27ae7a3927f 100644
> --- a/fs/ntfs/logfile.c
> +++ b/fs/ntfs/logfile.c
> @@ -27,7 +27,7 @@ static bool ntfs_check_restart_page_header(struct inode *vi,
> struct restart_page_header *rp, s64 pos)
> {
> u32 logfile_system_page_size, logfile_log_page_size;
> - u16 ra_ofs, usa_count, usa_ofs, usa_end = 0;
> + u32 ra_ofs, usa_count, usa_ofs, usa_end = 0;
> bool have_usa = true;
>
> ntfs_debug("Entering.");
>
> base-commit: 19dc08f1f2c5563ba4da6afd5ecace8eba163aef
>
Looks good to me.
Reviewed-by: Baolin Liu <liubaolin@kylinos.cn>
prev parent reply other threads:[~2026-10-21 1:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-20 13:44 Zhan Xusheng
2026-10-21 1:08 ` Hyunchul Lee
2026-10-21 1:16 ` liubaolin [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=754bcba2-2f8c-4bf5-8b12-16db8f485645@163.com \
--to=liubaolin12138@163.com \
--cc=hexlabsecurity@proton.me \
--cc=hyc.lee@gmail.com \
--cc=linkinjeon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ntfs@lists.linux.dev \
--cc=zhanxusheng1024@gmail.com \
--cc=zhanxusheng@xiaomi.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
all inboxes | Powered by JetHome®