From: Ali Ahmet Memis <ali@iusegentoo.com>
To: Alexander Viro <viro@zeniv.linux.org.uk>,
Christian Brauner <brauner@kernel.org>
Cc: Jan Kara <jack@suse.cz>, Kees Cook <kees@kernel.org>,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH 0/2] ufs: harden the mount path against malformed images
Date: Sat, 1 Aug 2026 10:12:56 +0300 [thread overview]
Message-ID: <20260801071306.59484-1-ali@iusegentoo.com> (raw)
Two robustness fixes for the ufs mount path, both reachable by mounting
a crafted UFS image.
Patch 1 reorders ufs_fill_super() so the root dentry is created after the
cylinder group metadata is loaded. Today a failure while reading the
cylinder groups drops UFS_SB(sb) but leaves s_root installed, so the
generic teardown oopses on a NULL pointer in ufs_sync_fs() and the
put_super operation.
Patch 2 validates the cylinder group index and the rotor positions in
ufs_read_cylinder() before they are cached. Unchecked, c_cgx indexes the
cylinder summary array (a 32 bit write outside s_csp), and the rotors
become bitmap scan offsets that can wrap an unsigned length and walk past
the cylinder group buffers during an ordinary allocation.
Mounting a ufs image needs CAP_SYS_ADMIN and ufs is not
unprivileged-mountable, so this is image-parsing hardening rather than a
privilege boundary, handled in the open like the recent sibling work:
ufs: reject malformed cylinder summary geometry
https://lore.kernel.org/all/20260701215700.822003-1-kudo3228@gmail.com/
ufs: reject oversized cylinder group metadata
https://lore.kernel.org/all/20260717104033.38574-1-david.lee@trailofbits.com/
Those validate fs_cssize and fs_cgsize in ufs_fill_super(); the checks
here live in ufs_read_cylinder() and do not overlap with them.
Both were reproduced under KASAN on an unpatched kernel by mounting a
crafted UFS2 image.
Patch 1, an image whose first cylinder group fails the magic check, so
ufs_read_cylinder_structures() fails after the root dentry is installed:
BUG: KASAN: null-ptr-deref in mutex_lock+0x76/0xe0
ufs_sync_fs+0x5b/0x6d0
BUG: kernel NULL pointer dereference, address: 0000000000000100
Patch 2, an image whose on-disk cg_cgx is out of range, followed by a
write that allocates a block:
BUG: KASAN: slab-out-of-bounds in adjust_free_blocks+0x1bf0/0x2510
adjust_free_blocks
With the patches applied, patch 1 loads the cylinder groups before
publishing the root dentry and patch 2 rejects the mismatched cg_cgx in
ufs_read_cylinder(), so neither faulting access is reached.
Ali Ahmet Memis (2):
ufs: create the root dentry after loading cylinder metadata
ufs: validate cylinder group metadata before caching it
fs/ufs/cylinder.c | 10 ++++++++++
fs/ufs/super.c | 17 +++++++++--------
2 files changed, 19 insertions(+), 8 deletions(-)
--
2.54.0
next reply other threads:[~2026-08-01 7:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-01 7:12 Ali Ahmet Memis [this message]
2026-08-01 7:12 ` [PATCH 1/2] ufs: create the root dentry after loading cylinder metadata Ali Ahmet Memis
2026-08-03 10:06 ` Jan Kara
2026-08-01 7:12 ` [PATCH 2/2] ufs: validate cylinder group metadata before caching it Ali Ahmet Memis
2026-08-03 10:10 ` Jan Kara
2026-08-25 12:42 ` [PATCH 0/2] ufs: harden the mount path against malformed images Christian Brauner
2026-08-25 12:50 ` Ali Ahmet Memis
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=20260801071306.59484-1-ali@iusegentoo.com \
--to=ali@iusegentoo.com \
--cc=brauner@kernel.org \
--cc=jack@suse.cz \
--cc=kees@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
/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®