From: patchwork-bot+netdevbpf@kernel.org
To: Xingwang Xiang <v3rdant.xiang@gmail.com>
Cc: john.fastabend@gmail.com, kuba@kernel.org, mrpre@163.com,
jakub@cloudflare.com, sd@queasysnail.net, davem@davemloft.net,
pabeni@redhat.com, horms@kernel.org, netdev@vger.kernel.org,
daniel@iogearbox.net, bpf@vger.kernel.org
Subject: Re: [PATCH net v5 0/2] bpf, skmsg: fix verdict sk_data_ready racing with ktls rx
Date: Thu, 21 May 2026 00:30:14 +0000 [thread overview]
Message-ID: <177932341489.3808433.10969832563832040180.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260517145630.20521-1-v3rdant.xiang@gmail.com>
Hello:
This series was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Sun, 17 May 2026 23:56:25 +0900 you wrote:
> sk_psock_verdict_data_ready() lacks the tls_sw_has_ctx_rx() guard that
> sk_psock_strp_data_ready() gained in e91de6afa81c. When a socket is
> inserted into a sockmap (BPF_SK_SKB_VERDICT) before TLS RX is configured,
> the missing guard causes tcp_read_skb() to drain sk_receive_queue without
> advancing copied_seq, leaving a dangling frag_list pointer that
> tls_decrypt_sg() walks — a use-after-free.
>
> [...]
Here is the summary with links:
- [net,v5,1/2] bpf, skmsg: fix verdict sk_data_ready racing with ktls rx
https://git.kernel.org/netdev/net/c/ddf8029623a1
- [net,v5,2/2] selftests/bpf: add regression test for ktls+sockmap verdict UAF
https://git.kernel.org/netdev/net/c/33644bd38aec
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:[~2026-05-21 0:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-17 14:56 [PATCH net v5 0/2] bpf, skmsg: fix verdict sk_data_ready racing with ktls rx Xingwang Xiang
2026-05-17 14:56 ` [PATCH net v5 1/2] " Xingwang Xiang
2026-05-17 14:56 ` [PATCH net v5 2/2] selftests/bpf: add regression test for ktls+sockmap verdict UAF Xingwang Xiang
2026-05-21 0: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=177932341489.3808433.10969832563832040180.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=horms@kernel.org \
--cc=jakub@cloudflare.com \
--cc=john.fastabend@gmail.com \
--cc=kuba@kernel.org \
--cc=mrpre@163.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sd@queasysnail.net \
--cc=v3rdant.xiang@gmail.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