From: patchwork-bot+netdevbpf@kernel.org
To: James Chapman <jchapman@katalix.com>
Cc: netdev@vger.kernel.org, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, linux-kernel@vger.kernel.org, pabeni@redhat.com,
syzkaller-bugs@googlegroups.com, tparkin@katalix.com,
hdanton@sina.com,
syzbot+b471b7c936301a59745b@syzkaller.appspotmail.com,
syzbot+c041b4ce3a6dfd1e63e2@syzkaller.appspotmail.com
Subject: Re: [PATCH net-next v2] l2tp: fix possible UAF when cleaning up tunnels
Date: Tue, 09 Jul 2024 09:40:31 +0000 [thread overview]
Message-ID: <172051803109.11180.9963479985374691387.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240704152508.1923908-1-jchapman@katalix.com>
Hello:
This patch was applied to netdev/net-next.git (main)
by Paolo Abeni <pabeni@redhat.com>:
On Thu, 4 Jul 2024 16:25:08 +0100 you wrote:
> syzbot reported a UAF caused by a race when the L2TP work queue closes a
> tunnel at the same time as a userspace thread closes a session in that
> tunnel.
>
> Tunnel cleanup is handled by a work queue which iterates through the
> sessions contained within a tunnel, and closes them in turn.
>
> [...]
Here is the summary with links:
- [net-next,v2] l2tp: fix possible UAF when cleaning up tunnels
https://git.kernel.org/netdev/net-next/c/f8ad00f3fb2a
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:[~2024-07-09 9:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-04 15:25 [PATCH net-next v2] l2tp: fix possible UAF when cleaning up tunnels James Chapman
2024-07-05 10:32 ` Hillf Danton
2024-07-08 10:06 ` James Chapman
2024-07-08 11:59 ` Hillf Danton
2024-07-08 13:57 ` James Chapman
2024-07-09 9:03 ` Paolo Abeni
2024-07-09 9:29 ` James Chapman
2024-07-09 9: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=172051803109.11180.9963479985374691387.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hdanton@sina.com \
--cc=jchapman@katalix.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=syzbot+b471b7c936301a59745b@syzkaller.appspotmail.com \
--cc=syzbot+c041b4ce3a6dfd1e63e2@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tparkin@katalix.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