All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Willem de Bruijn <willemdebruijn.kernel@gmail.com>
Cc: netdev@vger.kernel.org, davem@davemloft.net, kuba@kernel.org,
	edumazet@google.com, pabeni@redhat.com, horms@kernel.org,
	paul@xen.org, wei.liu@kernel.org, mst@redhat.com,
	axboe@kernel.dk, josef@toxicpanda.com, willemb@google.com
Subject: Re: [PATCH net-next] net: skbuff: replace ubuf_info ops ptr with type id
Date: Fri, 06 Nov 2026 22:50:18 +0000	[thread overview]
Message-ID: <179400541867.914342.2798395680614428990.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261103194625.1628600-1-willemdebruijn.kernel@gmail.com>

Hello:

This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:

On Tue,  3 Nov 2026 14:46:20 -0500 you wrote:
> From: Willem de Bruijn <willemb@google.com>
> 
> Avoid an easily corruptible callback pointer on skb linear
> out-of-bounds write bugs.
> 
> skb_shinfo(skb)->destructor_arg points to a struct ubuf_info, whose
> first member is a ubuf_info_ops vtable pointer. Corrupting
> skb_shared_info gives a trivial one-hop indirect call primitive via
> uarg->ops->complete.
> 
> [...]

Here is the summary with links:
  - [net-next] net: skbuff: replace ubuf_info ops ptr with type id
    https://git.kernel.org/netdev/net-next/c/ecca9bb2c855

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2026-11-06 22:50 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-03 19:46 [PATCH net-next] net: skbuff: replace ubuf_info ops ptr with type id Willem de Bruijn
2026-11-06 21:24 ` Jakub Kicinski
2026-11-06 21:31   ` Willem de Bruijn
2026-11-06 22: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=179400541867.914342.2798395680614428990.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=axboe@kernel.dk \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=horms@kernel.org \
    --cc=josef@toxicpanda.com \
    --cc=kuba@kernel.org \
    --cc=mst@redhat.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=paul@xen.org \
    --cc=wei.liu@kernel.org \
    --cc=willemb@google.com \
    --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.