From: CJ <firefly0158@163.com>
To: shaggy@kernel.org, yun.zhou@windriver.com, kees@kernel.org
Cc: jfs-discussion@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: [BUG] jfs: UBSAN shift-out-of-bounds in dbSplit
Date: Tue, 15 Sep 2026 15:51:10 +0800 (CST) [thread overview]
Message-ID: <4f5505ef.6e0f.1a0a40c62eb.Coremail.firefly0158@163.com> (raw)
Hi,
I am reporting a UBSAN shift-out-of-bounds in the JFS dmap split path, triggered
by a syzkaller reproducer that mounts a crafted JFS image. The issue is
reproducible with HEAD commit cee9395acd8043be0644b25c34bfa86623f2b935
(v7.3-rc1, Linux 7.3.0-rc1).
The reproducer mounts a crafted JFS filesystem image on a loop device and
allocates blocks, which makes the allocator split a dmap control page.
UBSAN reports a shift-out-of-bounds at fs/jfs/jfs_dmap.c:2728 with a shift
exponent of 121, which is far beyond the width of the 32-bit int being shifted.
The call path is dbSplit -> dbAllocBits -> dbAllocDmap -> dbAllocDmapLev. In the
original report the same report was recorded at fs/jfs/jfs_dmap.c:2707 with the
same shift exponent, so only the source line has moved.
One possible cause is that a value read from the dmap control page in the crafted
image is used as a shift amount without a range check, so the shift is undefined.
This looks like a missing validation of an on-disk field used in an arithmetic
expression. I am reporting the sanitizer finding and the path as observed.
This appears to be a recurrence of the syzbot issue whose external id is
eac84ce8b38992ca3441. It remains reproducible on v7.3-rc1.
Reproducer:
syz reproducer: https://pastebin.com/raw/K41rvWi8
console output: https://pastebin.com/raw/pUcm7xJB
kernel config: https://pastebin.com/raw/DmudbVCf
Kernel:
HEAD commit: cee9395acd8043be0644b25c34bfa86623f2b935
git tree: upstream (linux.git), tested through the v7.3-rc1 annotated tag object
e5e04726cdd043e309677071ab1b65a4b18f422b
kernel version: 7.3.0-rc1 #1 PREEMPT(full)
tested tag: v7.3-rc1 (Linux 7.3-rc1, 2026-08-30)
Let me know if you need more details or testing.
Best regards,
Changjian
reply other threads:[~2026-09-15 7:51 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4f5505ef.6e0f.1a0a40c62eb.Coremail.firefly0158@163.com \
--to=firefly0158@163.com \
--cc=jfs-discussion@lists.sourceforge.net \
--cc=kees@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=shaggy@kernel.org \
--cc=yun.zhou@windriver.com \
/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®