From: Konstantin Komarov <almaz.alexandrovich@paragon-software.com>
To: Jaehun Gou <p22gone@gmail.com>
Cc: <ntfs3@lists.linux.dev>, <linux-kernel@vger.kernel.org>,
Seunghun Han <kkamagui@gmail.com>,
Jihoon Kwon <kjh010315@gmail.com>
Subject: Re: [PATCH] fs: ntfs3: check return value of indx_find to avoid infinite loop
Date: Tue, 9 Dec 2025 14:36:17 +0100 [thread overview]
Message-ID: <ee6e02b3-9384-44f7-ab69-826be883d21c@paragon-software.com> (raw)
In-Reply-To: <20251202105959.1885454-1-p22gone@gmail.com>
On 12/2/25 11:59, Jaehun Gou wrote:
> We found an infinite loop bug in the ntfs3 file system that can lead to a
> Denial-of-Service (DoS) condition.
>
> A malformed dentry in the ntfs3 filesystem can cause the kernel to hang
> during the lookup operations. By setting the HAS_SUB_NODE flag in an
> INDEX_ENTRY within a directory's INDEX_ALLOCATION block and manipulating the
> VCN pointer, an attacker can cause the indx_find() function to repeatedly
> read the same block, allocating 4 KB of memory each time. The kernel lacks
> VCN loop detection and depth limits, causing memory exhaustion and an OOM
> crash.
>
> This patch adds a return value check for fnd_push() to prevent a memory
> exhaustion vulnerability caused by infinite loops. When the index exceeds the
> size of the fnd->nodes array, fnd_push() returns -EINVAL. The indx_find()
> function checks this return value and stops processing, preventing further
> memory allocation.
>
> Co-developed-by: Seunghun Han <kkamagui@gmail.com>
> Signed-off-by: Seunghun Han <kkamagui@gmail.com>
> Co-developed-by: Jihoon Kwon <kjh010315@gmail.com>
> Signed-off-by: Jihoon Kwon <kjh010315@gmail.com>
> Signed-off-by: Jaehun Gou <p22gone@gmail.com>
> ---
> fs/ntfs3/index.c | 7 ++++++-
> 1 file changed, 6 insertions(+), 1 deletion(-)
>
> diff --git a/fs/ntfs3/index.c b/fs/ntfs3/index.c
> index 6d1bf890929d..050b3709e020 100644
> --- a/fs/ntfs3/index.c
> +++ b/fs/ntfs3/index.c
> @@ -1190,7 +1190,12 @@ int indx_find(struct ntfs_index *indx, struct ntfs_inode *ni,
> return -EINVAL;
> }
>
> - fnd_push(fnd, node, e);
> + err = fnd_push(fnd, node, e);
> +
> + if (err) {
> + put_indx_node(node);
> + return err;
> + }
> }
>
> *entry = e;
Your patch has been applied. Thanks.
Regards,
Konstantin
prev parent reply other threads:[~2025-12-09 13:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-02 10:59 Jaehun Gou
2025-12-09 13:36 ` 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=ee6e02b3-9384-44f7-ab69-826be883d21c@paragon-software.com \
--to=almaz.alexandrovich@paragon-software.com \
--cc=kjh010315@gmail.com \
--cc=kkamagui@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ntfs3@lists.linux.dev \
--cc=p22gone@gmail.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®