Development discussion of WireGuard
 help / color / mirror / Atom feed
From: Nikolay Aleksandrov <razor@blackwall.org>
To: netdev@vger.kernel.org
Cc: Daniel Borkmann <daniel@iogearbox.net>,
	Martynas Pumputis <m@lambda.lt>,
	"Jason A . Donenfeld" <Jason@zx2c4.com>,
	wireguard@lists.zx2c4.com, kuba@kernel.org, davem@davemloft.net,
	Nikolay Aleksandrov <razor@blackwall.org>
Subject: [PATCH net 0/2] wireguard: device: fix metadata_dst xmit null pointer dereference
Date: Thu, 14 Apr 2022 13:44:56 +0300	[thread overview]
Message-ID: <20220414104458.3097244-1-razor@blackwall.org> (raw)

Hi,
Patch 01 fixes a null pointer dereference in wireguard's xmit path when
transmitting skbs with metadata_dst attached. Patch 02 adds a selftest for
that case using bpf_skb_set_tunnel_key on wg device's egress path.

Thanks,
 Nik

Nikolay Aleksandrov (2):
  wireguard: device: fix metadata_dst xmit null pointer dereference
  wireguard: selftests: add metadata_dst xmit selftest

 drivers/net/wireguard/device.c             |  3 +-
 tools/testing/selftests/wireguard/netns.sh | 63 ++++++++++++++++++++++
 2 files changed, 65 insertions(+), 1 deletion(-)

-- 
2.35.1


             reply	other threads:[~2022-04-22  0:21 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-14 10:44 Nikolay Aleksandrov [this message]
2022-04-14 10:44 ` [PATCH net 1/2] " Nikolay Aleksandrov
2022-04-14 11:28   ` Daniel Borkmann
2022-04-14 11:58   ` Jason A. Donenfeld
2022-04-14 10:44 ` [PATCH net 2/2] wireguard: selftests: add metadata_dst xmit selftest Nikolay Aleksandrov
2022-04-14 12:06   ` Jason A. Donenfeld
2022-04-14 12:12     ` Nikolay Aleksandrov
2022-04-14 12:24       ` Jason A. Donenfeld

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=20220414104458.3097244-1-razor@blackwall.org \
    --to=razor@blackwall.org \
    --cc=Jason@zx2c4.com \
    --cc=daniel@iogearbox.net \
    --cc=davem@davemloft.net \
    --cc=kuba@kernel.org \
    --cc=m@lambda.lt \
    --cc=netdev@vger.kernel.org \
    --cc=wireguard@lists.zx2c4.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;
as well as URLs for NNTP newsgroup(s).