From: patchwork-bot+netdevbpf@kernel.org
To: Cen Zhang (Microsoft) <blbllhy@gmail.com>
Cc: magnus.karlsson@intel.com, kerneljasonxing@gmail.com,
maciej.fijalkowski@intel.com, sdf@fomichev.me,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, horms@kernel.org, netdev@vger.kernel.org,
bpf@vger.kernel.org, linux-kernel@vger.kernel.org,
AutonomousCodeSecurity@microsoft.com,
tgopinath@linux.microsoft.com, kys@microsoft.com
Subject: Re: [PATCH net v4] xsk: fix NULL pointer dereference in __xsk_rcv()
Date: Wed, 19 Aug 2026 03:10:05 +0000 [thread overview]
Message-ID: <178710900561.2824559.3358618619338695557.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260813215328.99311-1-blbllhy@gmail.com>
Hello:
This patch was applied to netdev/net.git (main)
by David S. Miller <davem@davemloft.net>:
On Thu, 13 Aug 2026 17:53:28 -0400 you wrote:
> In the __xsk_rcv() multi-buffer path, xsk_buff_alloc() is called in a
> loop without checking its return value. xsk_buff_can_alloc() only
> counts fill queue entries without validating their addresses, so it
> can succeed while xsk_buff_alloc() rejects all remaining entries and
> returns NULL.
>
> Oops: general protection fault, probably for non-canonical address
> 0xdffffc0000000000
> KASAN: null-ptr-deref in range
> [0x0000000000000000-0x0000000000000007]
> RIP: 0010:__xsk_rcv+0x426/0xc20 (net/xdp/xsk.c:350)
> Call Trace:
> xsk_generic_rcv+0x26d/0x5f0
> xdp_do_generic_redirect+0x3c5/0xcf0
> do_xdp_generic+0x92f/0xe70
> __netif_receive_skb_core.constprop.0+0xf7e/0x2b30
>
> [...]
Here is the summary with links:
- [net,v4] xsk: fix NULL pointer dereference in __xsk_rcv()
https://git.kernel.org/netdev/net/c/73cee2bd5c96
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-08-19 3:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-13 21:53 [PATCH net v4] xsk: fix NULL pointer dereference in __xsk_rcv() Cen Zhang (Microsoft)
2026-08-17 14:10 ` Simon Horman
2026-08-19 0:08 ` Jason Xing
2026-08-19 3:10 ` 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=178710900561.2824559.3358618619338695557.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=AutonomousCodeSecurity@microsoft.com \
--cc=blbllhy@gmail.com \
--cc=bpf@vger.kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kerneljasonxing@gmail.com \
--cc=kuba@kernel.org \
--cc=kys@microsoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maciej.fijalkowski@intel.com \
--cc=magnus.karlsson@intel.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sdf@fomichev.me \
--cc=tgopinath@linux.microsoft.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