mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Konstantin Komarov <almaz.alexandrovich@paragon-software.com>
To: Weiming Shi <bestswngs@gmail.com>, <ntfs3@lists.linux.dev>
Cc: <linux-kernel@vger.kernel.org>, Xiang Mei <xmei5@asu.edu>
Subject: Re: [PATCH] fs/ntfs3: fix out-of-bounds read in read_log_rec_buf()
Date: Fri, 14 Aug 2026 08:54:39 +0200	[thread overview]
Message-ID: <b79286e5-05ef-4bff-bcfc-ed33c15ede43@paragon-software.com> (raw)
In-Reply-To: <20260623062230.1236506-2-bestswngs@gmail.com>

On 6/23/26 08:22, Weiming Shi wrote:

> [You don't often get email from bestswngs@gmail.com. Learn why this is important at https://aka.ms/LearnAboutSenderIdentification ]
>
> read_log_rec_buf() copies a log record into a caller buffer starting at
>
>          u32 off = lsn_to_page_off(log, lsn) + log->record_header_len;
>
> log->record_header_len (and log->data_off, used for the following pages)
> comes verbatim from the on-disk restart area and is only checked for
> 8-byte alignment in is_rst_area_valid(), so off can exceed
> log->page_size. "tail = log->page_size - off" then underflows and
> memcpy() reads past the page_size-sized buffer returned by
> read_log_page(), spilling adjacent slab memory into the replay buffer.
>
> This is reachable by mounting a crafted NTFS image:
>
>   BUG: KASAN: slab-out-of-bounds in read_log_rec_buf+0x216/0x580
>   Read of size 64 at addr ffff88800a877ff8 by task exploit/127
>    read_log_rec_buf fs/ntfs3/fslog.c:2299
>    log_replay fs/ntfs3/fslog.c:4216
>    ntfs_loadlog_and_replay fs/ntfs3/fsntfs.c:324
>    ntfs_fill_super fs/ntfs3/super.c:1392
>    get_tree_bdev_flags fs/super.c:1694
>    __x64_sys_mount fs/namespace.c:4360
>   The buggy address is located 4088 bytes to the right of
>   the 4096-byte region [ffff88800a876000, ffff88800a877000)
>
> Reject an in-page offset outside the current page before the copy.
>
> Fixes: b46acd6a6a62 ("fs/ntfs3: Add NTFS journal")
> Assisted-by: Claude:claude-opus-4-8
> Reported-by: Xiang Mei <xmei5@asu.edu>
> Signed-off-by: Weiming Shi <bestswngs@gmail.com>
> ---
>   fs/ntfs3/fslog.c | 10 +++++++++-
>   1 file changed, 9 insertions(+), 1 deletion(-)
>
> diff --git a/fs/ntfs3/fslog.c b/fs/ntfs3/fslog.c
> index f038c799e7ac..ee413dc80d3a 100644
> --- a/fs/ntfs3/fslog.c
> +++ b/fs/ntfs3/fslog.c
> @@ -2276,7 +2276,15 @@ static int read_log_rec_buf(struct ntfs_log *log,
>           */
>          for (;;) {
>                  bool usa_error;
> -               u32 tail = log->page_size - off;
> +               u32 tail;
> +
> +               /* off comes from the on-disk restart area; bound it. */
> +               if (off >= log->page_size) {
> +                       err = -EINVAL;
> +                       goto out;
> +               }
> +
> +               tail = log->page_size - off;
>
>                  if (tail >= data_len)
>                          tail = data_len;
> --
> 2.43.0

Hello,

Sorry for the delay.
Your patch was applied, thanks.

Regards,
Konstantin


      reply	other threads:[~2026-08-14  6:54 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-23  6:22 Weiming Shi
2026-08-14  6:54 ` Konstantin Komarov [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=b79286e5-05ef-4bff-bcfc-ed33c15ede43@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

all inboxes | Powered by JetHome®