Netdev List
 help / color / mirror / Atom feed
From: Jiayuan Chen <jiayuan.chen@linux.dev>
To: Sechang Lim <rhkrqnwk98@gmail.com>,
	willemdebruijn.kernel@gmail.com, davem@davemloft.net,
	edumazet@google.com, kuba@kernel.org, pabeni@redhat.com
Cc: horms@kernel.org, daniel@iogearbox.net, john.fastabend@gmail.com,
	jakub@cloudflare.com, aleksander.lobakin@intel.com,
	netdev@vger.kernel.org, bpf@vger.kernel.org,
	linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH net v2] udp: clear skb->dev before running a sockmap verdict
Date: Thu, 4 Jun 2026 09:49:21 +0800	[thread overview]
Message-ID: <b5d4d726-c32f-45e4-9ea7-28f7b6a1f8d7@linux.dev> (raw)
In-Reply-To: <20260603162737.697215-1-rhkrqnwk98@gmail.com>


On 6/4/26 12:27 AM, Sechang Lim wrote:
> On the UDP receive path skb->dev is repurposed as dev_scratch (the
> truesize/state cache set by udp_set_dev_scratch()), through the
> union { struct net_device *dev; unsigned long dev_scratch; } in sk_buff.
>
> When a UDP socket is in a sockmap, sk_data_ready is
> sk_psock_verdict_data_ready(), which calls udp_read_skb() -> recv_actor()
> (sk_psock_verdict_recv) to run the attached SK_SKB verdict program in softirq.
> If that program calls a socket-lookup helper (bpf_sk_lookup_tcp/udp,
> bpf_skc_lookup_tcp), bpf_skc_lookup() does:
>
> 	if (skb->dev)
> 		caller_net = dev_net(skb->dev);
>
> skb->dev still holds the dev_scratch value (a non-NULL integer), so dev_net()
> dereferences it as a struct net_device * and the kernel takes a general
> protection fault on a non-canonical address in softirq:
>
>    Oops: general protection fault, probably for non-canonical address 0x1010000800004a0
>    CPU: 1 UID: 0 PID: 1406 Comm: syz.2.19 Not tainted 7.1.0-rc6 #1 PREEMPT(full)
>    RIP: 0010:bpf_skc_lookup net/core/filter.c:7033 [inline]
>    RIP: 0010:bpf_sk_lookup+0x45/0x160 net/core/filter.c:7047
>    Call Trace:
>     <IRQ>
>     bpf_prog_4675cb904b7071f8+0x12e/0x14e
>     bpf_prog_run_pin_on_cpu+0xc6/0x1f0
>     sk_psock_verdict_recv+0x1ba/0x350
>     udp_read_skb+0x31a/0x370
>     sk_psock_verdict_data_ready+0x2e3/0x600
>     __udp_enqueue_schedule_skb+0x4c8/0x650
>     udpv6_queue_rcv_one_skb+0x3ec/0x740
>     udp6_unicast_rcv_skb+0x11d/0x140
>     ip6_protocol_deliver_rcu+0x61e/0x950
>     ip6_input_finish+0xa9/0x150
>     NF_HOOK+0x286/0x2f0
>     ip6_input+0x117/0x220
>     NF_HOOK+0x286/0x2f0
>     __netif_receive_skb+0x85/0x200
>     process_backlog+0x374/0x9a0
>     __napi_poll+0x4f/0x1c0
>     net_rx_action+0x3b0/0x770
>     handle_softirqs+0x15a/0x460
>     do_softirq+0x57/0x80
>     </IRQ>
>
> The rmem charge that dev_scratch accounted for is released by skb_recv_udp() on
> dequeue, just above, so the scratch is dead by the time recv_actor() runs. Clear
> skb->dev so bpf_skc_lookup() falls back to sock_net(skb->sk), which
> skb_set_owner_sk_safe() set just above.
>
> Fixes: 965b57b469a5 ("net: Introduce a new proto_ops ->read_skb()")
> Cc: stable@vger.kernel.org
> Signed-off-by: Sechang Lim <rhkrqnwk98@gmail.com>


Reviewed-by: Jiayuan Chen <jiayuan.chen@linux.dev>


  reply	other threads:[~2026-06-04  1:49 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-03 16:27 [PATCH net v2] udp: clear skb->dev before running a sockmap verdict Sechang Lim
2026-06-04  1:49 ` Jiayuan Chen [this message]
  -- strict thread matches above, loose matches on Subject: below --
2026-06-03 12:26 [PATCH net] " Sechang Lim
2026-06-03 16:21 ` [PATCH net v2] " Sechang Lim

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=b5d4d726-c32f-45e4-9ea7-28f7b6a1f8d7@linux.dev \
    --to=jiayuan.chen@linux.dev \
    --cc=aleksander.lobakin@intel.com \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=horms@kernel.org \
    --cc=jakub@cloudflare.com \
    --cc=john.fastabend@gmail.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=rhkrqnwk98@gmail.com \
    --cc=stable@vger.kernel.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox