NTFS3 file system kernel mode driver
 help / color / mirror / Atom feed
From: Konstantin Komarov <almaz.alexandrovich@paragon-software.com>
To: Weiming Shi <bestswngs@gmail.com>, <ntfs3@lists.linux.dev>
Cc: Xiang Mei <xmei5@asu.edu>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] fs/ntfs3: reject restart table growth beyond U16_MAX entries
Date: Tue, 28 Jul 2026 11:53:56 +0200	[thread overview]
Message-ID: <ab6feb90-2a8b-438e-b49b-cd30cf9ebecc@paragon-software.com> (raw)
In-Reply-To: <20260623101434.1321291-2-bestswngs@gmail.com>

On 6/23/26 12:14, Weiming Shi wrote:

> During $LogFile replay, log_replay() indexes the transaction table by the
> transact_id taken from the log record header.  check_log_rec() only
> verifies that transact_id is non-zero and properly aligned, not its
> magnitude, so a crafted image can request an arbitrarily large index.
>
> alloc_rsttbl_from_idx() grows the table to cover that index via
> extend_rsttbl(), which passes the new entry count to init_rsttbl():
>
>          rt = init_rsttbl(esize, used + add);
>
> used + add is computed as u32 but init_rsttbl() takes a u16, and the
> count is stored in struct RESTART_TABLE as a __le16.  When used + add
> exceeds U16_MAX it is truncated, init_rsttbl() allocates a table far
> smaller than the index requires, and alloc_rsttbl_from_idx() then
> dereferences and writes at the original, untruncated offset -- an
> out-of-bounds access past the allocation, reachable by mounting a
> crafted NTFS image.
>
>   BUG: KASAN: use-after-free in alloc_rsttbl_from_idx (fs/ntfs3/fslog.c:950)
>   Read of size 4 at addr ffff8880327ffff8 by task exploit
>    alloc_rsttbl_from_idx (fs/ntfs3/fslog.c:950)
>    log_replay (fs/ntfs3/fslog.c:4562)
>    ntfs_loadlog_and_replay (fs/ntfs3/fsntfs.c:324)
>    ntfs_fill_super (fs/ntfs3/super.c:1393)
>    get_tree_bdev_flags
>    vfs_get_tree
>    path_mount
>    __x64_sys_mount
>
> A restart table is limited to U16_MAX entries by its __le16 count, so a
> larger growth request is invalid input.  Reject it in extend_rsttbl();
> all callers already handle a NULL return.
>
> Fixes: b46acd6a6a62 ("fs/ntfs3: Add NTFS journal")
> Reported-by: Xiang Mei <xmei5@asu.edu>
> Assisted-by: Claude:claude-opus-4-8
> Signed-off-by: Weiming Shi <bestswngs@gmail.com>
> ---
>   fs/ntfs3/fslog.c | 3 +++
>   1 file changed, 3 insertions(+)
>
> diff --git a/fs/ntfs3/fslog.c b/fs/ntfs3/fslog.c
> index f038c799e7ac..78f34442aaaa 100644
> --- a/fs/ntfs3/fslog.c
> +++ b/fs/ntfs3/fslog.c
> @@ -853,6 +853,9 @@ static inline struct RESTART_TABLE *extend_rsttbl(struct RESTART_TABLE *tbl,
>          u32 used = le16_to_cpu(tbl->used);
>          struct RESTART_TABLE *rt;
>
> +       if (used + add > U16_MAX)
> +               return NULL;
> +
>          rt = init_rsttbl(esize, used + add);
>          if (!rt)
>                  return NULL;
> --
> 2.43.0
>
Hello,

Sorry for the delay.
Your patch was applied, thank you.

Regards,
Konstantin


  reply	other threads:[~2026-07-28  9:54 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-23 10:14 [PATCH] fs/ntfs3: reject restart table growth beyond U16_MAX entries Weiming Shi
2026-07-28  9:53 ` Konstantin Komarov [this message]
2026-07-28 10:29   ` Weiming Shi

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=ab6feb90-2a8b-438e-b49b-cd30cf9ebecc@paragon-software.com \
    --to=almaz.alexandrovich@paragon-software.com \
    --cc=bestswngs@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ntfs3@lists.linux.dev \
    --cc=xmei5@asu.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