From: syzbot <syzbot+0962e3a1af6d5e26a52c@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Forwarded: [PATCH] bpf: defer bpffs symlink inode freeing until RCU grace period
Date: Fri, 29 May 2026 17:40:55 -0700 [thread overview]
Message-ID: <6a1a3217.abb04025.19af7b.0005.GAE@google.com> (raw)
In-Reply-To: <6a19f098.abb04025.19af7b.0004.GAE@google.com>
For archival purposes, forwarding an incoming command email to
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com.
***
Subject: [PATCH] bpf: defer bpffs symlink inode freeing until RCU grace period
Author: hongao@uniontech.com
#syz test
bpffs currently frees inodes directly from ->destroy_inode(). This can race
with RCU path walk following a bpffs symlink: a lookup reader may still hold
an unstable inode pointer while unlink frees the inode memory, leading to a
KASAN use-after-free in security_inode_follow_link().
Keep BPF object reference dropping in ->destroy_inode(), where sleeping
cleanup is allowed, but move symlink target and inode memory freeing to
->free_inode() so VFS releases them after an RCU grace period.
Fixes: 4f375ade6aa9 ("bpf: Avoid RCU context warning when unpinning htab with internal structs")
Reported-by: syzbot+0962e3a1af6d5e26a52c@syzkaller.appspotmail.com
Signed-off-by: hongao <hongao@uniontech.com>
---
kernel/bpf/inode.c | 9 +++++++--
1 file changed, 7 insertions(+), 2 deletions(-)
diff --git a/kernel/bpf/inode.c b/kernel/bpf/inode.c
index 25c06a011825..a1e9660f9237 100644
--- a/kernel/bpf/inode.c
+++ b/kernel/bpf/inode.c
@@ -766,10 +766,14 @@ static void bpf_destroy_inode(struct inode *inode)
{
enum bpf_type type;
- if (S_ISLNK(inode->i_mode))
- kfree(inode->i_link);
if (!bpf_inode_type(inode, &type))
bpf_any_put(inode->i_private, type);
+}
+
+static void bpf_free_inode(struct inode *inode)
+{
+ if (S_ISLNK(inode->i_mode))
+ kfree(inode->i_link);
free_inode_nonrcu(inode);
}
@@ -778,6 +782,7 @@ const struct super_operations bpf_super_ops = {
.drop_inode = inode_just_drop,
.show_options = bpf_show_options,
.destroy_inode = bpf_destroy_inode,
+ .free_inode = bpf_free_inode,
};
enum {
--
2.51.0
next prev parent reply other threads:[~2026-05-30 0:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-29 20:01 [syzbot] [lsm?] KASAN: slab-use-after-free Read in security_inode_follow_link syzbot
2026-05-30 0:40 ` syzbot [this message]
2026-05-30 6:13 ` Hillf Danton
2026-05-30 6:33 ` syzbot
2026-05-30 9:51 ` Hillf Danton
2026-05-30 10:47 ` syzbot
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=6a1a3217.abb04025.19af7b.0005.GAE@google.com \
--to=syzbot+0962e3a1af6d5e26a52c@syzkaller.appspotmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=syzkaller-bugs@googlegroups.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
Powered by JetHome