From: DaeMyung Kang <charsyam@gmail.com>
To: Namjae Jeon <linkinjeon@kernel.org>, Hyunchul Lee <hyc.lee@gmail.com>
Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
DaeMyung Kang <charsyam@gmail.com>
Subject: [PATCH v2 0/3] ntfs: harden MFT record and attribute parsing
Date: Sat, 9 May 2026 15:12:34 +0900 [thread overview]
Message-ID: <20260509061237.3233714-1-charsyam@gmail.com> (raw)
In-Reply-To: <20260508153410.2624801-1-charsyam@gmail.com>
This series tightens fs/ntfs against malformed on-disk metadata and
fixes one off-by-one in the MFT bitmap scan.
Patches 1/3 and 3/3 are complementary: 1/3 rejects MFT records whose
attrs_offset points past bytes_in_use at record entry, and 3/3 moves
the per-attribute name bounds check earlier so it covers the AT_UNUSED
enumeration path that hands the name pointer back to callers. Without
3/3, two enumeration paths can read past an attribute record: one in
fs/ntfs/attrib.c passes the returned name pointer to ntfs_attr_iget(),
and another in fs/ntfs/inode.c copies the name while building an
attribute list.
Patch 2/3 is independent: ntfs_mft_record_layout() rejects
mft_no >= 2^32, but the bitmap scan in
ntfs_mft_bitmap_find_and_alloc_free_rec_nolock() used '>'. Bring it in
line with the other 2^32 boundary checks in fs/ntfs/mft.c.
All three carry the same upstream Fixes tag (1da177e4c3f4) since the
issues date from the initial upstream import of fs/ntfs.
Changes since v1:
- All patches: replaced the OOT Fixes tag d3ad708fecaa ("ntfs:
Initial commit") with the upstream commit 1da177e4c3f4
("Linux-2.6.12-rc2"), since checkpatch flagged the v1 commit id
as unknown to mainline and all three issues date from the initial
fs/ntfs import.
- 2/3: removed the OOT-only "#if LINUX_VERSION_CODE >= KERNEL_VERSION(
6, 6, 0)" guard that surrounded the folio_unlock()/kunmap_local()/
folio_put() block; mainline does not need it and it prevented the
patch from applying.
- 1/3, 3/3: no functional change.
v1: https://lore.kernel.org/linux-ntfs/20260508153410.2624801-1-charsyam@gmail.com/
DaeMyung Kang (3):
ntfs: validate MFT attrs_offset against bytes_in_use
ntfs: fix MFT bitmap scan 2^32 boundary check
ntfs: validate attribute name bounds before returning it
fs/ntfs/attrib.c | 25 +++++++++++++++++--------
fs/ntfs/mft.c | 15 +++++++++++++--
2 files changed, 30 insertions(+), 10 deletions(-)
base-commit: 70390501d1944d4e5b8f7352be180fceb3a44132
--
2.43.0
next prev parent reply other threads:[~2026-05-09 6:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-08 15:34 [PATCH 0/3] ntfs: harden MFT record and attribute parsing DaeMyung Kang
2026-05-08 15:34 ` [PATCH 1/3] ntfs: validate MFT attrs_offset against bytes_in_use DaeMyung Kang
2026-05-08 15:34 ` [PATCH 2/3] ntfs: fix MFT bitmap scan 2^32 boundary check DaeMyung Kang
2026-05-09 4:03 ` Namjae Jeon
2026-05-09 6:14 ` CharSyam
2026-05-08 15:34 ` [PATCH 3/3] ntfs: validate attribute name bounds before returning it DaeMyung Kang
2026-05-09 6:12 ` DaeMyung Kang [this message]
2026-05-09 15:44 ` [PATCH v2 0/3] ntfs: harden MFT record and attribute parsing Namjae Jeon
2026-05-09 6:12 ` [PATCH v2 1/3] ntfs: validate MFT attrs_offset against bytes_in_use DaeMyung Kang
2026-05-09 6:12 ` [PATCH v2 2/3] ntfs: fix MFT bitmap scan 2^32 boundary check DaeMyung Kang
2026-05-09 6:12 ` [PATCH v2 3/3] ntfs: validate attribute name bounds before returning it DaeMyung Kang
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=20260509061237.3233714-1-charsyam@gmail.com \
--to=charsyam@gmail.com \
--cc=hyc.lee@gmail.com \
--cc=linkinjeon@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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