From: patchwork-bot+netdevbpf@kernel.org
To: Kyle Zeng <kylebot@openai.com>
Cc: netdev@vger.kernel.org, davem@davemloft.net, edumazet@kernel.org,
kuba@kernel.org, pabeni@redhat.com, linux-kernel@vger.kernel.org,
outbounddisclosures@openai.com
Subject: Re: [PATCH] net: skbuff: preserve fclone lifetime when freeing stolen heads
Date: Mon, 09 Nov 2026 23:30:20 +0000 [thread overview]
Message-ID: <179426702076.3543549.4583782076046363502.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261030042329.74461-1-kylebot@openai.com>
Hello:
This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Thu, 29 Oct 2026 21:23:29 -0700 you wrote:
> skb_morph() can give an skb from skbuff_fclone_cache a page-fragment
> head without changing its fclone tag. IPv4 reassembly can produce such
> an skb, which can subsequently reach the GRO stolen-head path.
>
> napi_skb_free_stolen_head() puts the shell into the ordinary NAPI skb
> cache without dropping its fclone_ref. If the embedded companion is
> still live, KASAN poisons it along with the original, and later cache
> reuse or eviction can overwrite or free the allocation underneath it.
> A mirrored batman-adv DAT packet retained in a plug qdisc reproduces a
> KASAN use-after-free in plug_dequeue().
>
> [...]
Here is the summary with links:
- net: skbuff: preserve fclone lifetime when freeing stolen heads
https://git.kernel.org/netdev/net/c/86706ffa990e
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-11-09 23:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-30 4:23 Kyle Zeng
2026-10-30 4:30 ` netdev-bot+sinfo
2026-11-09 23: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=179426702076.3543549.4583782076046363502.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
all inboxes | Powered by JetHome®