From: patchwork-bot+netdevbpf@kernel.org
To: Kyle Zeng <kylebot@openai.com>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
davem@davemloft.net, edumazet@kernel.org, kuba@kernel.org,
pabeni@redhat.com, outbounddisclosures@openai.com
Subject: Re: [PATCH net] netlink: reset skb headers before unicast and multicast filtering
Date: Tue, 13 Oct 2026 09:50:04 +0000 [thread overview]
Message-ID: <179188500427.177823.5830234053974309894.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261006224232.50724-1-kylebot@openai.com>
Hello:
This patch was applied to netdev/net.git (main)
by Paolo Abeni <pabeni@redhat.com>:
On Tue, 6 Oct 2026 15:42:32 -0700 you wrote:
> Socket filters can use SKF_NET_OFF and SKF_LL_OFF to read relative to
> an skb's network and MAC headers. Netlink producers may reserve
> headroom without resetting those headers, allowing a receiving socket's
> filter to read data before the initialized message.
>
> For example, IWPM HELLO replies are allocated with dev_alloc_skb(),
> which reserves NET_SKB_PAD bytes. An unprivileged NETLINK_RDMA user can
> attach a classic socket filter and disclose this headroom through the
> length of the delivered reply. The resets in netlink_dump() do not help
> because IWPM sends a separately allocated skb through netlink_unicast().
>
> [...]
Here is the summary with links:
- [net] netlink: reset skb headers before unicast and multicast filtering
https://git.kernel.org/netdev/net/c/8bf659bd54e1
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-10-13 9:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-06 22:42 [PATCH net] netlink: reset skb headers before unicast and multicast filtering Kyle Zeng
2026-10-06 22:55 ` netdev-bot+sinfo
2026-10-07 5:17 ` Kyle Zeng
2026-10-07 5:19 ` Kyle Zeng
2026-10-13 9:50 ` 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=179188500427.177823.5830234053974309894.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@kernel.org \
--cc=kuba@kernel.org \
--cc=kylebot@openai.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=outbounddisclosures@openai.com \
--cc=pabeni@redhat.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