From: CJ <firefly0158@163.com>
To: jaegeuk@kernel.org, chao@kernel.org
Cc: linux-f2fs-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org,
syzbot+0b1e85354f790743db08@syzkaller.appspotmail.com
Subject: [BUG] f2fs: possible KASAN use-after-free in f2fs_iget on v7.2-rc3
Date: Thu, 3 Sep 2026 11:14:28 +0800 (CST) [thread overview]
Message-ID: <d1f8ae2.2f3a.1a06542c0ac.Coremail.firefly0158@163.com> (raw)
Hi,
I am reporting a possible recurrence of a KASAN use-after-free triggered
by a syzkaller reproducer on Linux 7.2-rc3. The issue is reproducible
with HEAD commit a13c140cc289c0b7b3770bce5b3ad42ab35074aa.
The reproducer mounts a crafted F2FS filesystem image and invokes
open_by_handle_at() with a malformed file handle. This reaches
f2fs_nfs_get_inode() and f2fs_iget(), where the inode and its extent
cache are initialized and validated.
The archived target crash report shows a use-after-free read in
sanity_check_inode(), called from do_read_inode() and f2fs_iget(). The
affected object belongs to the f2fs_extent_tree cache. It was allocated
by f2fs_init_extent_tree() and freed by f2fs_destroy_extent_tree()
during inode eviction.
This looks like an extent-tree lifetime issue in an f2fs_iget() error
path. A stale extent_tree pointer may remain accessible after a failed
inode lookup causes the inode and its extent tree to be evicted.
This appears related to the following previously reported issue, which
was originally observed on Linux 5.15:
https://syzkaller.appspot.com/bug?extid=0b1e85354f790743db08
Reproducer:
syz reproducer: https://pastebin.com/raw/LGCbYiqL
console output: https://pastebin.com/raw/FzSecFbT
kernel config: https://pastebin.com/raw/PZsF562V
Kernel:
HEAD commit: a13c140cc289c0b7b3770bce5b3ad42ab35074aa
git tree: torvalds/linux
kernel version: 7.2.0-rc3 #1 PREEMPT(full)
tested tag: v7.2-rc3
Let me know if you need more details or testing.
Best regards
reply other threads:[~2026-09-03 3:15 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=d1f8ae2.2f3a.1a06542c0ac.Coremail.firefly0158@163.com \
--to=firefly0158@163.com \
--cc=chao@kernel.org \
--cc=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=syzbot+0b1e85354f790743db08@syzkaller.appspotmail.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®