From: patchwork-bot+netdevbpf@kernel.org
To: Kuniyuki Iwashima <kuniyu@amazon.com>
Cc: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, pablo@netfilter.org, laforge@gnumonks.org,
ap420073@gmail.com, kuni1840@gmail.com, netdev@vger.kernel.org,
osmocom-net-gprs@lists.osmocom.org, syzkaller@googlegroups.com
Subject: Re: [PATCH v1 net] gtp: Fix use-after-free in __gtp_encap_destroy().
Date: Sat, 24 Jun 2023 22:30:19 +0000 [thread overview]
Message-ID: <168764581981.27285.13297166277839266868.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230622213231.24651-1-kuniyu@amazon.com>
Hello:
This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Thu, 22 Jun 2023 14:32:31 -0700 you wrote:
> syzkaller reported use-after-free in __gtp_encap_destroy(). [0]
>
> It shows the same process freed sk and touched it illegally.
>
> Commit e198987e7dd7 ("gtp: fix suspicious RCU usage") added lock_sock()
> and release_sock() in __gtp_encap_destroy() to protect sk->sk_user_data,
> but release_sock() is called after sock_put() releases the last refcnt.
>
> [...]
Here is the summary with links:
- [v1,net] gtp: Fix use-after-free in __gtp_encap_destroy().
https://git.kernel.org/netdev/net/c/ce3aee7114c5
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:[~2023-06-24 22:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-22 21:32 [PATCH v1 net] gtp: Fix use-after-free in __gtp_encap_destroy() Kuniyuki Iwashima
2023-06-22 21:38 ` Pablo Neira Ayuso
2023-06-23 9:48 ` Jiri Pirko
2023-06-24 22:30 ` 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=168764581981.27285.13297166277839266868.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=ap420073@gmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=kuni1840@gmail.com \
--cc=kuniyu@amazon.com \
--cc=laforge@gnumonks.org \
--cc=netdev@vger.kernel.org \
--cc=osmocom-net-gprs@lists.osmocom.org \
--cc=pabeni@redhat.com \
--cc=pablo@netfilter.org \
--cc=syzkaller@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;
as well as URLs for NNTP newsgroup(s).