From: tobgaertner <tob.gaertner@me.com>
To: almaz.alexandrovich@paragon-software.com
Cc: ntfs3@lists.linux.dev, linux-kernel@vger.kernel.org,
stable@vger.kernel.org, security@kernel.org,
Tobias Gaertner <tob.gaertner@me.com>
Subject: [PATCH 0/2] ntfs3: fix OOB read and integer overflow in run_unpack()
Date: Sun, 29 Mar 2026 04:17:01 -0700 [thread overview]
Message-ID: <20260329111704.411449-1-tob.gaertner@me.com> (raw)
From: Tobias Gaertner <tob.gaertner@me.com>
Two bugs in run_unpack() found by fuzzing with a source-patched harness
(LibAFL + QEMU ARM64 system-mode):
Patch 1: run_unpack() checks `run_buf < run_last` at the loop top but
then reads size_size and offset_size bytes via run_unpack_s64() without
verifying they fit in the remaining buffer. A crafted NTFS image with
truncated run data triggers a heap OOB read of up to 15 bytes on mount.
Patch 2: The volume boundary check `lcn + len > sbi->used.bitmap.nbits`
uses raw addition that can wrap for large values, bypassing the
validation. CVE-2025-40068 added check_add_overflow() for adjacent
arithmetic but missed this instance.
Both bugs are present since NTFS3 was merged in 5.15.
Could CVE IDs be assigned for these two issues?
tobgaertner (2):
ntfs3: add buffer boundary checks to run_unpack()
ntfs3: fix integer overflow in run_unpack() volume boundary check
fs/ntfs3/run.c | 18 +++++++++++++++---
1 file changed, 15 insertions(+), 3 deletions(-)
--
2.43.0
next reply other threads:[~2026-03-29 11:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-29 11:17 tobgaertner [this message]
2026-03-29 11:17 ` [PATCH 1/2] ntfs3: add buffer boundary checks to run_unpack() tobgaertner
2026-03-29 11:17 ` [PATCH 2/2] ntfs3: fix integer overflow in run_unpack() volume boundary check tobgaertner
2026-04-07 17:19 ` [PATCH 0/2] ntfs3: fix OOB read and integer overflow in run_unpack() Konstantin Komarov
2026-04-15 4:19 ` Tobias Gaertner
2026-04-15 7:00 ` Willy Tarreau
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=20260329111704.411449-1-tob.gaertner@me.com \
--to=tob.gaertner@me.com \
--cc=almaz.alexandrovich@paragon-software.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ntfs3@lists.linux.dev \
--cc=security@kernel.org \
--cc=stable@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
all inboxes | Powered by JetHome®