From: Al Viro <viro@zeniv.linux.org.uk>
To: Alexei Starovoitov <alexei.starovoitov@gmail.com>
Cc: Deepanshu Kartikey <kartikey406@gmail.com>,
Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
Andrii Nakryiko <andrii@kernel.org>,
Martin KaFai Lau <martin.lau@linux.dev>,
Eduard <eddyz87@gmail.com>,
Kumar Kartikeya Dwivedi <memxor@gmail.com>,
Song Liu <song@kernel.org>,
Yonghong Song <yonghong.song@linux.dev>,
Jiri Olsa <jolsa@kernel.org>, KaFai Wan <kafai.wan@linux.dev>,
bpf <bpf@vger.kernel.org>, LKML <linux-kernel@vger.kernel.org>,
Christian Brauner <brauner@kernel.org>, Jan Kara <jack@suse.cz>,
syzbot+36e50496c8ac4bcde3f9@syzkaller.appspotmail.com
Subject: Re: [PATCH v2] bpf: fix UAF by restoring RCU-delayed inode freeing in bpffs
Date: Tue, 2 Jun 2026 04:10:58 +0100 [thread overview]
Message-ID: <20260602031058.GQ2636677@ZenIV> (raw)
In-Reply-To: <CAADnVQ+TAm1Mow5sHej5wUGz7j+BLSxw9gGwgP6rP1cw8cRXPA@mail.gmail.com>
On Mon, Jun 01, 2026 at 07:54:35PM -0700, Alexei Starovoitov wrote:
> > Fixes: 4f375ade6aa9 ("bpf: Avoid RCU context warning when unpinning htab with internal structs")
> > Reported-by: syzbot+36e50496c8ac4bcde3f9@syzkaller.appspotmail.com
> > Closes: https://syzkaller.appspot.com/bug?extid=36e50496c8ac4bcde3f9
> > Suggested-by: Al Viro <viro@zeniv.linux.org.uk>
> > Link: https://lore.kernel.org/all/20260423043906.GN3518998@ZenIV/
> > Link: https://lore.kernel.org/all/20260602002607.110866-1-kartikey406@gmail.com/T/ [v1]
> > Signed-off-by: Deepanshu Kartikey <kartikey406@gmail.com>
> > ---
> > Changes in v2:
> > - NAK on v1 fix in fs/namei.c (pick_link) by Al Viro
> > - v1 was papering over the symptom not fixing root cause
> > - real fix is in kernel/bpf/inode.c as suggested by Al Viro
> Al,
> please ack.
Acked-by: Al Viro <viro@zeniv.linux.org.uk>
My apologies - should've followed up on that myself after your
reply in the original thread, but that has fallen through the
cracks ;-/
next prev parent reply other threads:[~2026-06-02 3:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-02 2:52 Deepanshu Kartikey
2026-06-02 2:54 ` Alexei Starovoitov
2026-06-02 3:10 ` Al Viro [this message]
2026-06-02 4:10 ` patchwork-bot+netdevbpf
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=20260602031058.GQ2636677@ZenIV \
--to=viro@zeniv.linux.org.uk \
--cc=alexei.starovoitov@gmail.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=brauner@kernel.org \
--cc=daniel@iogearbox.net \
--cc=eddyz87@gmail.com \
--cc=jack@suse.cz \
--cc=jolsa@kernel.org \
--cc=kafai.wan@linux.dev \
--cc=kartikey406@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.lau@linux.dev \
--cc=memxor@gmail.com \
--cc=song@kernel.org \
--cc=syzbot+36e50496c8ac4bcde3f9@syzkaller.appspotmail.com \
--cc=yonghong.song@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