All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Jakub Kicinski <kuba@kernel.org>
Cc: davem@davemloft.net, netdev@vger.kernel.org, edumazet@google.com,
	pabeni@redhat.com, andrew+netdev@lunn.ch, horms@kernel.org,
	ncardwell@google.com, kuniyu@google.com, daniel.zahka@gmail.com,
	willemb@google.com
Subject: Re: [PATCH net-next] net: psp: don't assume reply skbs will have a socket
Date: Fri, 03 Oct 2025 18:00:14 +0000	[thread overview]
Message-ID: <175951441449.20895.2740639730759580288.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20251001022426.2592750-1-kuba@kernel.org>

Hello:

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

On Tue, 30 Sep 2025 19:24:26 -0700 you wrote:
> Rx path may be passing around unreferenced sockets, which means
> that skb_set_owner_edemux() may not set skb->sk and PSP will crash:
> 
>   KASAN: null-ptr-deref in range [0x0000000000000010-0x0000000000000017]
>   RIP: 0010:psp_reply_set_decrypted (./include/net/psp/functions.h:132 net/psp/psp_sock.c:287)
>     tcp_v6_send_response.constprop.0 (net/ipv6/tcp_ipv6.c:979)
>     tcp_v6_send_reset (net/ipv6/tcp_ipv6.c:1140 (discriminator 1))
>     tcp_v6_do_rcv (net/ipv6/tcp_ipv6.c:1683)
>     tcp_v6_rcv (net/ipv6/tcp_ipv6.c:1912)
> 
> [...]

Here is the summary with links:
  - [net-next] net: psp: don't assume reply skbs will have a socket
    https://git.kernel.org/netdev/net/c/7a0f94361ffd

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



      parent reply	other threads:[~2025-10-03 18:00 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-01  2:24 [PATCH net-next] net: psp: don't assume reply skbs will have a socket Jakub Kicinski
2025-10-02  6:28 ` Kuniyuki Iwashima
2025-10-02  6:41   ` Eric Dumazet
2025-10-03 18:00 ` 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=175951441449.20895.2740639730759580288.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=andrew+netdev@lunn.ch \
    --cc=daniel.zahka@gmail.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=horms@kernel.org \
    --cc=kuba@kernel.org \
    --cc=kuniyu@google.com \
    --cc=ncardwell@google.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=willemb@google.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.