mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Konstantin Komarov <almaz.alexandrovich@paragon-software.com>
To: Hyeontae Lee <wonju345@naver.com>, <ntfs3@lists.linux.dev>
Cc: <linux-kernel@vger.kernel.org>, <stable@vger.kernel.org>
Subject: Re: [PATCH] fs/ntfs3: bound CreateAttribute asize against record_size in do_action
Date: Fri, 16 Oct 2026 16:47:55 +0200	[thread overview]
Message-ID: <2cb5b61a-f16b-4dcb-b7f2-73409da192df@paragon-software.com> (raw)
In-Reply-To: <20260731141440.52168-1-wonju345@naver.com>

On 7/31/26 16:14, Hyeontae Lee wrote:

> In do_action()'s CreateAttribute case (fslog.c:3286), attr2 points into
> the on-disk log record and asize = le32_to_cpu(attr2->size) is therefore
> attacker-controlled on mount.  The guard bounds asize only against the
> log record itself,
>
>          Add2Ptr(attr2, asize) > Add2Ptr(lrh, rec_len)
>
> where rec_len is the client data length, and separately bounds dlen
> against the MFT record.  Nothing bounds asize against record_size, but
> all three writes that follow are into rec, a kmalloc(sbi->record_size)
> buffer allocated by mi_init() (record.c:105):
>
>          memmove(Add2Ptr(attr, asize), attr, used - roff);
>          memcpy(attr, attr2, asize);
>          rec->used = cpu_to_le32(used + asize);
>
> With record_size 0x400, roff 0x38, used 0x160 and asize 0x800 the memcpy
> writes 2048 bytes at rec + 0x38, 0x438 bytes past the allocation, and
> rec->used is left at 0x960.  dlen is 0x18 here, so the existing
> dlen check passes: dlen bounds nothing about the size of the copy.
>
> The equivalent non-replay path already refuses this.  mi_insert_attr()
> performs the same insert and starts with (record.c:488):
>
>          if (used + asize > sbi->record_size)
>                  return NULL;
>
> Apply the same bound, spelled as a subtraction to match the neighbouring
> clause.  used <= record_size holds here because check_file_record()
> validates it (fslog.c:2826) and is called on this record at fslog.c:3172;
> roff <= used - 4 follows from check_if_attr() together with the ATTR_END
> check at fslog.c:2844, so bounding used + asize bounds both copies.
>
> The sibling WriteEndOfFileRecordSegment case does the equivalent check
> against record_size at fslog.c:3277.
>
> Reproduced by mounting a crafted image on v7.2-rc5 under KASAN:
>
>    BUG: KASAN: slab-out-of-bounds in do_action.isra.0+0x41f6/0x83a0
>    Write of size 2048 at addr ffff888005c74838 by task mount/69
>
>    CPU: 0 UID: 0 PID: 69 Comm: mount Not tainted 7.2.0-rc5-00300-g8ba098e6b6ff #2
>    Call Trace:
>     kasan_report+0xce/0x100
>     kasan_check_range+0x105/0x1b0
>     __asan_memcpy+0x3c/0x60
>     do_action.isra.0+0x41f6/0x83a0
>     log_replay+0x920a/0xd300
>     ntfs_loadlog_and_replay+0x3ef/0x510
>     ntfs_fill_super+0x1d23/0x4550
>     get_tree_bdev_flags+0x2ef/0x550
>     vfs_get_tree+0x82/0x2f0
>     fc_mount+0x10/0x1b0
>     path_mount+0x517/0x1df0
>     __x64_sys_mount+0x20b/0x270
>     do_syscall_64+0xf9/0x540
>     entry_SYSCALL_64_after_hwframe+0x77/0x7f
>
>    Allocated by task 69:
>     __kasan_kmalloc+0x8f/0xa0
>     __kmalloc_noprof+0x1b4/0x460
>     mi_init+0x81/0x110
>     mi_get+0x6a/0x220
>     do_action.isra.0+0x1db4/0x83a0
>     log_replay+0x920a/0xd300
>     ntfs_loadlog_and_replay+0x3ef/0x510
>     ntfs_fill_super+0x1d23/0x4550
>
>    The buggy address belongs to the object at ffff888005c74800
>     which belongs to the cache kmalloc-1k of size 1024
>    The buggy address is located 56 bytes inside of
>     allocated 1024-byte region [ffff888005c74800, ffff888005c74c00)
>
> Fixes: b46acd6a6a62 ("fs/ntfs3: Add NTFS journal")
> Cc: stable@vger.kernel.org
> Assisted-by: Claude:claude-opus-5
> Signed-off-by: Hyeontae Lee <wonju345@naver.com>
> ---
>   fs/ntfs3/fslog.c | 7 ++++++-
>   1 file changed, 6 insertions(+), 1 deletion(-)
>
> diff --git a/fs/ntfs3/fslog.c b/fs/ntfs3/fslog.c
> index f038c799e7ac..2230a4a77872 100644
> --- a/fs/ntfs3/fslog.c
> +++ b/fs/ntfs3/fslog.c
> @@ -3288,10 +3288,15 @@ static int do_action(struct ntfs_log *log, struct OPEN_ATTR_ENRTY *oe,
>                  asize = le32_to_cpu(attr2->size);
>                  used = le32_to_cpu(rec->used);
>
> +               /*
> +                * attr2->size is taken from the log record and is bounded only
> +                * by the log record length, not by the MFT record.  Refuse an
> +                * attribute that does not fit, as mi_insert_attr() does.
> +                */
>                  if (!check_if_attr(rec, lrh) || dlen < SIZEOF_RESIDENT ||
>                      !IS_ALIGNED(asize, 8) ||
>                      Add2Ptr(attr2, asize) > Add2Ptr(lrh, rec_len) ||
> -                   dlen > record_size - used) {
> +                   dlen > record_size - used || asize > record_size - used) {
>                          goto dirty_vol;
>                  }
>
> --
> 2.43.0

Hello,

Your patch was applied, thanks.

Regards,
Konstantin


      reply	other threads:[~2026-10-16 14:48 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-31 14:14 Hyeontae Lee
2026-10-16 14:47 ` 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=2cb5b61a-f16b-4dcb-b7f2-73409da192df@paragon-software.com \
    --to=almaz.alexandrovich@paragon-software.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ntfs3@lists.linux.dev \
    --cc=stable@vger.kernel.org \
    --cc=wonju345@naver.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®