From: Hillf Danton <hdanton@sina.com>
To: syzbot <syzbot+aef8e425f1a85ee5ef1c@syzkaller.appspotmail.com>
Cc: linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [kernel?] KASAN: slab-use-after-free Read in task_work_run
Date: Sat, 1 Mar 2025 08:05:51 +0800 [thread overview]
Message-ID: <20250301000552.2827-1-hdanton@sina.com> (raw)
In-Reply-To: <67c099eb.050a0220.222324.026a.GAE@google.com>
On Thu, 27 Feb 2025 08:59:23 -0800
> syzbot found the following issue on:
>
> HEAD commit: 63817c771194 selftests/bpf: Test struct_ops program with _..
> git tree: bpf-next
> syz repro: https://syzkaller.appspot.com/x/repro.syz?x=12d306e4580000
#syz test
--- x/kernel/events/core.c
+++ y/kernel/events/core.c
@@ -5368,6 +5368,7 @@ static void _free_event(struct perf_even
exclusive_event_destroy(event);
module_put(event->pmu->module);
+ perf_pending_task_sync(event);
call_rcu(&event->rcu_head, free_event_rcu);
}
--
next prev parent reply other threads:[~2025-03-01 0:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-27 16:59 [syzbot] [kernel?] KASAN: slab-use-after-free Read in task_work_run syzbot
2025-03-01 0:05 ` Hillf Danton [this message]
2025-03-01 0:31 ` 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=20250301000552.2827-1-hdanton@sina.com \
--to=hdanton@sina.com \
--cc=linux-kernel@vger.kernel.org \
--cc=syzbot+aef8e425f1a85ee5ef1c@syzkaller.appspotmail.com \
--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