From: Joseph Qi <joseph.qi@linux.alibaba.com>
To: Michael Bommarito <michael.bommarito@gmail.com>,
akpm <akpm@linux-foundation.org>
Cc: ZhengYuan Huang <gality369@gmail.com>,
ocfs2-devel@lists.linux.dev, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org, Mark Fasheh <mark@fasheh.com>,
Joel Becker <jlbec@evilplan.org>
Subject: Re: [PATCH 2/3] ocfs2: reject dinodes whose i_rdev disagrees with the file type
Date: Mon, 18 May 2026 09:37:37 +0800 [thread overview]
Message-ID: <ead6ed9a-e198-48aa-bb63-03049a3b08b9@linux.alibaba.com> (raw)
In-Reply-To: <20260517111015.3187935-3-michael.bommarito@gmail.com>
On 5/17/26 7:10 PM, Michael Bommarito wrote:
> id1.dev1.i_rdev is the device-number arm of the ocfs2_dinode id1
> union and is only meaningful for character and block device
> inodes. For any other user-visible file type the on-disk value
> must be zero.
>
> ocfs2_populate_inode() currently runs
>
> inode->i_rdev = huge_decode_dev(le64_to_cpu(fe->id1.dev1.i_rdev));
>
> unconditionally, before the S_IFMT switch decides whether the
> inode is a special file. As a result, an i_rdev value present on
> a non-device inode is silently published into the in-core inode.
> A subsequent forced re-read or in-core mode mutation (cluster
> peer with raw write access to the shared LUN, on-disk corruption,
> or a separately forged dinode) can then expose the attacker-
> controlled device number to init_special_inode() without ever
> showing an unusual i_mode at validation time.
>
> System inodes (OCFS2_SYSTEM_FL) legitimately use the bitmap1 and
> journal1 arms of the same union: allocator inodes encode i_used
> / i_total in the bitmap1 arm and the journal encodes ij_flags /
> ij_recovery_generation in the journal1 arm. Those byte
> sequences are not an i_rdev and a non-zero pattern there is the
> on-disk norm, not an integrity violation. Restrict the cross-
> check to non-system inodes; that is the full surface where
> i_rdev semantics apply and is also the full surface an
> unprivileged consumer of the volume can see.
>
> Following the i_mode canonicalisation in patch 1, S_ISCHR /
> S_ISBLK covers the whole device-inode space; this check operates
> correctly on its own, but the canonicalised i_mode makes the
> predicate exhaustive.
>
> Fixes: b657c95c1108 ("ocfs2: Wrap inode block reads in a dedicated function.")
> Cc: stable@vger.kernel.org
> Signed-off-by: Michael Bommarito <michael.bommarito@gmail.com>
> Assisted-by: Claude:claude-opus-4-7
Looks fine.
Reviewed-by: Joseph Qi <joseph.qi@linux.alibaba.com>
> ---
> fs/ocfs2/inode.c | 38 ++++++++++++++++++++++++++++++++++++++
> 1 file changed, 38 insertions(+)
>
> diff --git a/fs/ocfs2/inode.c b/fs/ocfs2/inode.c
> index fb592bf3e5f31..305e22cc9b1d9 100644
> --- a/fs/ocfs2/inode.c
> +++ b/fs/ocfs2/inode.c
> @@ -1533,6 +1533,44 @@ int ocfs2_validate_inode_block(struct super_block *sb,
> }
> }
>
> + /*
> + * id1.dev1.i_rdev is the device-number arm of the id1 union and
> + * is only meaningful for character and block device inodes. For
> + * any other regular user-visible file type the on-disk value
> + * must be zero. ocfs2_populate_inode() currently runs
> + *
> + * inode->i_rdev = huge_decode_dev(le64_to_cpu(fe->id1.dev1.i_rdev));
> + *
> + * unconditionally, before the S_IFMT switch decides whether the
> + * inode is a special file. As a result, an i_rdev value present
> + * on a non-device inode is silently published into the in-core
> + * inode; a subsequent forced re-read or in-core mode mutation
> + * (cluster peer with raw write access to the shared LUN,
> + * on-disk corruption, or a separately forged dinode) can then
> + * expose the attacker-controlled device number to
> + * init_special_inode() without ever showing an unusual i_mode
> + * at validation time.
> + *
> + * System inodes (OCFS2_SYSTEM_FL) legitimately use the bitmap1
> + * and journal1 arms of the same union (allocator i_used /
> + * i_total counters and the journal ij_flags /
> + * ij_recovery_generation pair); those bytes are not an i_rdev
> + * and must not be checked here. Restrict the cross-check to
> + * non-system inodes, which is the full attacker-controllable
> + * surface.
> + */
> + if (!(le32_to_cpu(di->i_flags) & OCFS2_SYSTEM_FL) &&
> + !S_ISCHR(le16_to_cpu(di->i_mode)) &&
> + !S_ISBLK(le16_to_cpu(di->i_mode)) &&
> + di->id1.dev1.i_rdev != 0) {
> + rc = ocfs2_error(sb,
> + "Invalid dinode #%llu: non-device mode 0%o with i_rdev %llu\n",
> + (unsigned long long)bh->b_blocknr,
> + le16_to_cpu(di->i_mode),
> + (unsigned long long)le64_to_cpu(di->id1.dev1.i_rdev));
> + goto bail;
> + }
> +
> if (le16_to_cpu(di->i_dyn_features) & OCFS2_INLINE_DATA_FL) {
> struct ocfs2_inline_data *data = &di->id2.i_data;
>
next prev parent reply other threads:[~2026-05-18 1:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-17 11:10 [PATCH 0/3] ocfs2: harden inode validators against forged metadata Michael Bommarito
2026-05-17 11:10 ` [PATCH 1/3] ocfs2: reject dinodes with non-canonical i_mode type or stray bits Michael Bommarito
2026-05-18 1:36 ` Joseph Qi
2026-05-17 11:10 ` [PATCH 2/3] ocfs2: reject dinodes whose i_rdev disagrees with the file type Michael Bommarito
2026-05-18 1:37 ` Joseph Qi [this message]
2026-05-17 11:10 ` [PATCH 3/3] ocfs2: reject regular files with non-zero i_size and zero i_clusters Michael Bommarito
2026-05-18 1:38 ` Joseph Qi
2026-05-18 21:40 ` [PATCH 0/3] ocfs2: harden inode validators against forged metadata Andrew Morton
2026-05-19 0:57 ` Michael Bommarito
2026-06-01 17:39 ` Joel Becker
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=ead6ed9a-e198-48aa-bb63-03049a3b08b9@linux.alibaba.com \
--to=joseph.qi@linux.alibaba.com \
--cc=akpm@linux-foundation.org \
--cc=gality369@gmail.com \
--cc=jlbec@evilplan.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark@fasheh.com \
--cc=michael.bommarito@gmail.com \
--cc=ocfs2-devel@lists.linux.dev \
/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
Powered by JetHome