From: Henry Martin <bsdhenrymartin@gmail.com>
To: Carlos Maiolino <cem@kernel.org>,
"Darrick J . Wong" <djwong@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Alex Deucher <alexander.deucher@amd.com>,
David Hildenbrand <david@kernel.org>,
Kairui Song <kasong@tencent.com>,
James Clark <james.clark@linaro.org>,
Long Li <leo.lilong@huawei.com>,
Kevin Brodsky <kevin.brodsky@arm.com>,
Javier Tia <javier@peridio.com>, SJ Park <sj@kernel.org>,
Rafal Ostrowski <rafal.ostrowski@amd.com>,
Myeonghun Pak <mhun512@gmail.com>, Likun Gao <Likun.Gao@amd.com>,
hongao <hongao@uniontech.com>,
Kees Cook <kees+treewide@kernel.org>,
Cihan Karadag <cihan.cihan@gmail.com>
Cc: linux-xfs@vger.kernel.org, linux-kernel@vger.kernel.org,
Henry Martin <bsdhenrymartin@gmail.com>,
stable@vger.kernel.org
Subject: [PATCH] xfs: fix out-of-bounds da node read with a crafted record count
Date: Tue, 27 Oct 2026 23:17:54 +0800 [thread overview]
Message-ID: <20261027151754.975492-1-bsdhenrymartin@gmail.com> (raw)
xfs_da3_node_verify() bounds the on-disk record count with:
/* we don't know if the node is for and attribute or directory
* tree, so only fail if the count is outside both bounds
*/
if (ichdr.count > mp->m_dir_geo->node_ents &&
ichdr.count > mp->m_attr_geo->node_ents)
return __this_address;
The "fail only outside both bounds" conjunction is forced weak
because the verify pass cannot tell directory from attribute nodes.
On filesystems with a multi-fsb directory block size (mkfs.xfs -n
size=64k, sb_dirblklog > 0), m_dir_geo->node_ents is much larger than
m_attr_geo->node_ents (~8184 vs ~504 for 64k/4k), so an attribute
tree node with a count in (attr_ents, dir_ents] passes verification.
Consumers then index the in-block btree array with that count and
read out of bounds:
xfs_da3_node_lookup_int() btree[max - 1].hashval (max = count)
xfs_da3_path_shift() btree[nodehdr.count - 1].hashval / .before
with count=8184 the read lands ~61KB past the 4K buffer, and the
out-of-bounds "before" value is then used as a child block number.
The read path is reachable by an unprivileged user via
getxattr/listxattr once the malicious image is mounted.
Tightening the verify conjunction would falsely reject legitimate
large directory nodes whose counts live in the same interval, so
enforce the per-fork bound instead where the geometry is known: at
the two consumers that index the array with the on-disk count.
This issue was discovered by Tencent CodeBuddy Security.
Fixes: f5ea110044fa ("xfs: add CRCs to dir2/da node blocks")
Cc: stable@vger.kernel.org
Signed-off-by: Henry Martin <bsdhenrymartin@gmail.com>
---
fs/xfs/libxfs/xfs_da_btree.c | 16 ++++++++++++++++
1 file changed, 16 insertions(+)
diff --git a/fs/xfs/libxfs/xfs_da_btree.c b/fs/xfs/libxfs/xfs_da_btree.c
index 3d02a0d7ba44a..ab3deff11111e 100644
--- a/fs/xfs/libxfs/xfs_da_btree.c
+++ b/fs/xfs/libxfs/xfs_da_btree.c
@@ -1787,6 +1787,18 @@ xfs_da3_node_lookup_int(
} else
expected_level--;
+ /* The verify pass cannot tell directory from attribute
+ * nodes, so its count bound has to allow both geometries.
+ * Here we know the fork; enforce its geometry so crafted
+ * counts cannot make the array indexing run out of the
+ * block.
+ */
+ if (nodehdr.count > args->geo->node_ents) {
+ xfs_buf_mark_corrupt(blk->bp);
+ xfs_da_mark_sick(args);
+ return -EFSCORRUPTED;
+ }
+
max = nodehdr.count;
blk->hashval = be32_to_cpu(btree[max - 1].hashval);
@@ -2161,6 +2173,11 @@ xfs_da3_path_shift(
blk = &path->blk[level];
xfs_da3_node_hdr_from_disk(dp->i_mount, &nodehdr,
blk->bp->b_addr);
+ if (nodehdr.count > args->geo->node_ents) {
+ xfs_buf_mark_corrupt(blk->bp);
+ xfs_da_mark_sick(args);
+ return -EFSCORRUPTED;
+ }
if (forward && (blk->index < nodehdr.count - 1)) {
blk->index++;
@@ -2227,6 +2244,11 @@ xfs_da3_path_shift(
blk->magic = XFS_DA_NODE_MAGIC;
xfs_da3_node_hdr_from_disk(dp->i_mount, &nodehdr,
bp->b_addr);
+ if (nodehdr.count > args->geo->node_ents) {
+ xfs_buf_mark_corrupt(blk->bp);
+ xfs_da_mark_sick(args);
+ return -EFSCORRUPTED;
+ }
btree = nodehdr.btree;
blk->hashval = be32_to_cpu(btree[nodehdr.count - 1].hashval);
if (forward)
--
2.43.7
next reply other threads:[~2026-10-27 15:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-27 15:17 Henry Martin [this message]
2026-10-28 22:49 ` Dave Chinner
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=20261027151754.975492-1-bsdhenrymartin@gmail.com \
--to=bsdhenrymartin@gmail.com \
--cc=Likun.Gao@amd.com \
--cc=akpm@linux-foundation.org \
--cc=alexander.deucher@amd.com \
--cc=cem@kernel.org \
--cc=cihan.cihan@gmail.com \
--cc=david@kernel.org \
--cc=djwong@kernel.org \
--cc=hongao@uniontech.com \
--cc=james.clark@linaro.org \
--cc=javier@peridio.com \
--cc=kasong@tencent.com \
--cc=kees+treewide@kernel.org \
--cc=kevin.brodsky@arm.com \
--cc=leo.lilong@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=mhun512@gmail.com \
--cc=rafal.ostrowski@amd.com \
--cc=sj@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®