From: Kees Cook <kees@kernel.org>
To: lei lu <llfamsec@gmail.com>
Cc: almaz.alexandrovich@paragon-software.com, ntfs3@lists.linux.dev
Subject: Re: [PATCH] ntfs3: Add bounds checking for dp0
Date: Mon, 8 Jul 2024 12:52:12 -0700 [thread overview]
Message-ID: <202407081244.99EB198E@keescook> (raw)
In-Reply-To: <20240701102935.3018-1-llfamsec@gmail.com>
On Mon, Jul 01, 2024 at 06:29:35PM +0800, lei lu wrote:
> Added out-of-bound checking for *dp0 (DIR_PAGE_ENTRY_32).
>
> Signed-off-by: lei lu <llfamsec@gmail.com>
> ---
> fs/ntfs3/fslog.c | 12 ++++++++----
> 1 file changed, 8 insertions(+), 4 deletions(-)
>
> diff --git a/fs/ntfs3/fslog.c b/fs/ntfs3/fslog.c
> index 855519713bf7..af6f2ce9ea68 100644
> --- a/fs/ntfs3/fslog.c
> +++ b/fs/ntfs3/fslog.c
> @@ -4184,10 +4184,14 @@ int log_replay(struct ntfs_inode *ni, bool *initialized)
> dp = NULL;
> while ((dp = enum_rstbl(dptbl, dp))) {
> struct DIR_PAGE_ENTRY_32 *dp0 = (struct DIR_PAGE_ENTRY_32 *)dp;
> - // NOTE: Danger. Check for of boundary.
> - memmove(&dp->vcn, &dp0->vcn_low,
> - 2 * sizeof(u64) +
> - le32_to_cpu(dp->lcns_follow) * sizeof(u64));
> + // Check for of boundary.
> + u32 len = 2 * sizeof(u64) +
> + le32_to_cpu(dp->lcns_follow) * sizeof(u64);
Can't this calculation still overflow?
> + if (PtrOffset(dptbl, &dp0->vcn_low) + len > t32) {
> + err = -EINVAL;
> + goto out;
> + }
> + memmove(&dp->vcn, &dp0->vcn_low, len);
> }
Hmm, I think this code has not been exercised under CONFIG_FORTIFY_SOURCE.
This would immediately WARN at run-time: dp->vcn is a u64. This is
writing beyond the member. Likely this needs to be split up:
struct DIR_PAGE_ENTRY {
__le32 next; // 0x00: RESTART_ENTRY_ALLOCATED if allocated
__le32 target_attr; // 0x04: Index into the Open attribute Table
__le32 transfer_len; // 0x08:
__le32 lcns_follow; // 0x0C:
__le64 vcn; // 0x10: Vcn of dirty page
__le64 oldest_lsn; // 0x18:
__le64 page_lcns[]; // 0x20:
};
struct DIR_PAGE_ENTRY_32 {
__le32 next; // 0x00: RESTART_ENTRY_ALLOCATED if allocated
__le32 target_attr; // 0x04: Index into the Open attribute Table
__le32 transfer_len; // 0x08:
__le32 lcns_follow; // 0x0C:
__le32 reserved; // 0x10:
__le32 vcn_low; // 0x14: Vcn of dirty page
__le32 vcn_hi; // 0x18: Vcn of dirty page
__le32 oldest_lsn_low; // 0x1C:
__le32 oldest_lsn_hi; // 0x1C:
__le32 page_lcns_low; // 0x24:
__le32 page_lcns_hi; // 0x24:
};
dp->vcn = ((u64)dp0->vcn_high << 32U | dp0->vcn_low);
dp->oldest_lsn = ((u64)dp0->oldest_lsn_high << 32U | dp0->oldest_lsn_low);
memmove(dp->page_lcns, dp0->...?, ...)
--
Kees Cook
next prev parent reply other threads:[~2024-07-08 19:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-01 10:29 [PATCH] ntfs3: Add bounds checking for dp0 lei lu
2024-07-08 19:52 ` Kees Cook [this message]
2024-07-09 3:16 ` lei lu
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=202407081244.99EB198E@keescook \
--to=kees@kernel.org \
--cc=almaz.alexandrovich@paragon-software.com \
--cc=llfamsec@gmail.com \
--cc=ntfs3@lists.linux.dev \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.