From: Konstantin Komarov <almaz.alexandrovich@paragon-software.com>
To: Xiang Mei <xmei5@asu.edu>, <ntfs3@lists.linux.dev>
Cc: <linux-kernel@vger.kernel.org>, Weiming Shi <bestswngs@gmail.com>
Subject: Re: [PATCH ntfs3] fs/ntfs3: validate $SDH entry size in ntfs_insert_security
Date: Mon, 21 Sep 2026 12:54:14 +0200 [thread overview]
Message-ID: <f15662b4-eb81-432c-8f4c-ed62a230bbab@paragon-software.com> (raw)
In-Reply-To: <20260703215431.73681-1-xmei5@asu.edu>
On 7/3/26 23:54, Xiang Mei wrote:
> ntfs_insert_security() walks the $Secure::$SDH index and reads
> e->sec_hdr.size for every entry returned by indx_find()/indx_find_sort().
> Those only guarantee the NTFS_DE envelope (e->size), so a crafted $SDH
> entry shorter than a full NTFS_DE_SDH at the tail of an index buffer makes
> the read of e->sec_hdr.size run past the allocation. Triggerable by an
> unprivileged setxattr(2) on a crafted NTFS image.
>
> BUG: KASAN: slab-out-of-bounds in ntfs_insert_security (fs/ntfs3/fsntfs.c:2148)
> Read of size 4 at addr ffff88800fa1de00 by task exploit/142
> ntfs_insert_security (fs/ntfs3/fsntfs.c:2148)
> ntfs_setxattr (fs/ntfs3/xattr.c:947)
> __vfs_setxattr (fs/xattr.c:223)
> __vfs_setxattr_noperm (fs/xattr.c:257)
> vfs_setxattr (fs/xattr.c:344)
> filename_setxattr (fs/xattr.c:690)
> path_setxattrat (fs/xattr.c:734)
> __x64_sys_setxattr (fs/xattr.c:764)
> [...]
> The buggy address is located 0 bytes to the right of
> allocated 512-byte region [ffff88800fa1dc00, ffff88800fa1de00)
>
> Stop the scan when an entry is too small to hold a SECURITY_HDR.
>
> Fixes: 82cae269cfa9 ("fs/ntfs3: Add initialization of super block")
> Reported-by: Weiming Shi <bestswngs@gmail.com>
> Signed-off-by: Xiang Mei <xmei5@asu.edu>
> ---
> fs/ntfs3/fsntfs.c | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/fs/ntfs3/fsntfs.c b/fs/ntfs3/fsntfs.c
> index bc7469d0a34d..6d81ae6c1f11 100644
> --- a/fs/ntfs3/fsntfs.c
> +++ b/fs/ntfs3/fsntfs.c
> @@ -2145,6 +2145,9 @@ int ntfs_insert_security(struct ntfs_sb_info *sbi,
> goto out;
>
> while (e) {
> + if (le16_to_cpu(e->de.size) < SIZEOF_SDH_DIRENTRY)
> + break;
> +
> if (le32_to_cpu(e->sec_hdr.size) == new_sec_size) {
> err = ntfs_read_run_nb(sbi, &ni->file.run,
> le64_to_cpu(e->sec_hdr.off),
Hello,
Sorry for the delay.
Your patch is applied, thank you.
Regards,
Konstantin
prev parent reply other threads:[~2026-09-21 10:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-03 21:54 Xiang Mei
2026-09-21 10: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=f15662b4-eb81-432c-8f4c-ed62a230bbab@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®