From: patchwork-bot+netdevbpf@kernel.org
To: Ignat Korchagin <ignat@cloudflare.com>
Cc: davem@davemloft.net, dsahern@kernel.org, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, revest@chromium.org,
kernel-team@cloudflare.com, kuniyu@amazon.com,
stable@vger.kernel.org
Subject: Re: [PATCH net v3] net: do not leave a dangling sk pointer, when socket creation fails
Date: Thu, 20 Jun 2024 09:20:28 +0000 [thread overview]
Message-ID: <171887522859.13884.11995426221933987830.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240617210205.67311-1-ignat@cloudflare.com>
Hello:
This patch was applied to netdev/net.git (main)
by Paolo Abeni <pabeni@redhat.com>:
On Mon, 17 Jun 2024 22:02:05 +0100 you wrote:
> It is possible to trigger a use-after-free by:
> * attaching an fentry probe to __sock_release() and the probe calling the
> bpf_get_socket_cookie() helper
> * running traceroute -I 1.1.1.1 on a freshly booted VM
>
> A KASAN enabled kernel will log something like below (decoded and stripped):
> ==================================================================
> BUG: KASAN: slab-use-after-free in __sock_gen_cookie (./arch/x86/include/asm/atomic64_64.h:15 ./include/linux/atomic/atomic-arch-fallback.h:2583 ./include/linux/atomic/atomic-instrumented.h:1611 net/core/sock_diag.c:29)
> Read of size 8 at addr ffff888007110dd8 by task traceroute/299
>
> [...]
Here is the summary with links:
- [net,v3] net: do not leave a dangling sk pointer, when socket creation fails
https://git.kernel.org/netdev/net/c/6cd4a78d962b
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-06-20 9:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-17 21:02 [PATCH net v3] net: do not leave a dangling sk pointer, when socket creation fails Ignat Korchagin
2024-06-17 21:15 ` Kuniyuki Iwashima
2024-06-19 12:31 ` D. Wythe
2024-06-19 13:08 ` Ignat Korchagin
2024-06-19 14:34 ` Ignat Korchagin
2024-06-19 15:13 ` Jakub Kicinski
2024-06-20 9:20 ` 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=171887522859.13884.11995426221933987830.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=ignat@cloudflare.com \
--cc=kernel-team@cloudflare.com \
--cc=kuba@kernel.org \
--cc=kuniyu@amazon.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=revest@chromium.org \
--cc=stable@vger.kernel.org \
/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.