From: patchwork-bot+netdevbpf@kernel.org
To: Bingquan Chen <patzilla007@gmail.com>
Cc: willemdebruijn.kernel@gmail.com, gregkh@linuxfoundation.org,
stephen@networkplumber.org, security@kernel.org,
davem@davemloft.net, kuba@kernel.org, edumazet@google.com,
netdev@vger.kernel.org
Subject: Re: [PATCH net] net/packet: fix TOCTOU race on mmap'd vnet_hdr in tpacket_snd()
Date: Thu, 23 Apr 2026 03:40:09 +0000 [thread overview]
Message-ID: <177691560954.4145271.18164483820935848818.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260418112006.78823-1-patzilla007@gmail.com>
Hello:
This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Sat, 18 Apr 2026 19:20:06 +0800 you wrote:
> In tpacket_snd(), when PACKET_VNET_HDR is enabled, vnet_hdr points
> directly into the mmap'd TX ring buffer shared with userspace. The
> kernel validates the header via __packet_snd_vnet_parse() but then
> re-reads all fields later in virtio_net_hdr_to_skb(). A concurrent
> userspace thread can modify the vnet_hdr fields between validation
> and use, bypassing all safety checks.
>
> [...]
Here is the summary with links:
- [net] net/packet: fix TOCTOU race on mmap'd vnet_hdr in tpacket_snd()
https://git.kernel.org/netdev/net/c/2c054e17d9d4
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:[~2026-04-23 3:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <2026041858-estimator-shower-0f16@gregkh>
2026-04-18 11:20 ` [PATCH net] net/packet: fix TOCTOU race on mmap'd vnet_hdr in tpacket_snd() Bingquan Chen
2026-04-18 20:17 ` Willem de Bruijn
2026-04-23 3:40 ` patchwork-bot+netdevbpf [this message]
2026-04-17 8:15 [PATCH] " Willem de Bruijn
2026-04-17 13:36 ` [PATCH net] " Zero Mark
2026-04-17 20:01 ` Willem de Bruijn
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=177691560954.4145271.18164483820935848818.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=gregkh@linuxfoundation.org \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=patzilla007@gmail.com \
--cc=security@kernel.org \
--cc=stephen@networkplumber.org \
--cc=willemdebruijn.kernel@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 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.