From: patchwork-bot+netdevbpf@kernel.org
To: Schspa Shi <schspa@gmail.com>
Cc: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, Jason@zx2c4.com, djwong@kernel.org,
jack@suse.cz, hca@linux.ibm.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org,
syzbot+6fd64001c20aa99e34a4@syzkaller.appspotmail.com
Subject: Re: [PATCH] mrp: introduce active flags to prevent UAF when applicant uninit
Date: Fri, 18 Nov 2022 12:40:17 +0000 [thread overview]
Message-ID: <166877521703.4012.15281131262381117062.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20221116114511.7720-1-schspa@gmail.com>
Hello:
This patch was applied to netdev/net-next.git (master)
by David S. Miller <davem@davemloft.net>:
On Wed, 16 Nov 2022 19:45:11 +0800 you wrote:
> The caller of del_timer_sync must prevent restarting of the timer, If
> we have no this synchronization, there is a small probability that the
> cancellation will not be successful.
>
> And syzbot report the fellowing crash:
> ==================================================================
> BUG: KASAN: use-after-free in hlist_add_head include/linux/list.h:929 [inline]
> BUG: KASAN: use-after-free in enqueue_timer+0x18/0xa4 kernel/time/timer.c:605
> Write at addr f9ff000024df6058 by task syz-fuzzer/2256
> Pointer tag: [f9], memory tag: [fe]
>
> [...]
Here is the summary with links:
- mrp: introduce active flags to prevent UAF when applicant uninit
https://git.kernel.org/netdev/net-next/c/ab0377803daf
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2022-11-18 12:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-16 11:45 [PATCH] mrp: introduce active flags to prevent UAF when applicant uninit Schspa Shi
2022-11-18 12:40 ` patchwork-bot+netdevbpf [this message]
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=166877521703.4012.15281131262381117062.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=Jason@zx2c4.com \
--cc=davem@davemloft.net \
--cc=djwong@kernel.org \
--cc=edumazet@google.com \
--cc=hca@linux.ibm.com \
--cc=jack@suse.cz \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=schspa@gmail.com \
--cc=syzbot+6fd64001c20aa99e34a4@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.