From: patchwork-bot+netdevbpf@kernel.org
To: Daniel Borkmann <daniel@iogearbox.net>
Cc: martin.lau@kernel.org, bpf@vger.kernel.org,
netdev@vger.kernel.org, xten@osec.io, v4bel@theori.io,
qwerty@theori.io
Subject: Re: [PATCH bpf 1/2] bpf: Fix too early release of tcx_entry
Date: Mon, 08 Jul 2024 22:30:33 +0000 [thread overview]
Message-ID: <172047783313.17442.16042215164463451364.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240708133130.11609-1-daniel@iogearbox.net>
Hello:
This series was applied to bpf/bpf.git (master)
by Martin KaFai Lau <martin.lau@kernel.org>:
On Mon, 8 Jul 2024 15:31:29 +0200 you wrote:
> Pedro Pinto and later independently also Hyunwoo Kim and Wongi Lee reported
> an issue that the tcx_entry can be released too early leading to a use
> after free (UAF) when an active old-style ingress or clsact qdisc with a
> shared tc block is later replaced by another ingress or clsact instance.
>
> Essentially, the sequence to trigger the UAF (one example) can be as follows:
>
> [...]
Here is the summary with links:
- [bpf,1/2] bpf: Fix too early release of tcx_entry
https://git.kernel.org/bpf/bpf/c/1cb6f0bae504
- [bpf,2/2] selftests/bpf: Extend tcx tests to cover late tcx_entry release
https://git.kernel.org/bpf/bpf/c/5f1d18de7918
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2024-07-08 22:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-08 13:31 [PATCH bpf 1/2] bpf: Fix too early release of tcx_entry Daniel Borkmann
2024-07-08 13:31 ` [PATCH bpf 2/2] selftests/bpf: Extend tcx tests to cover late tcx_entry release Daniel Borkmann
2024-07-08 22:34 ` Martin KaFai Lau
2024-07-09 19:48 ` Daniel Borkmann
2024-07-08 22:30 ` patchwork-bot+netdevbpf [this message]
2024-07-09 0:21 ` [PATCH bpf 1/2] bpf: Fix too early release of tcx_entry John Fastabend
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=172047783313.17442.16042215164463451364.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=martin.lau@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=qwerty@theori.io \
--cc=v4bel@theori.io \
--cc=xten@osec.io \
/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