All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel.org>
To: Todd Bert Freed <toddfreed@meta.com>
Cc: netdev-bot+sashiko@kernel.org, netdev@vger.kernel.org,
	borisp@nvidia.com, saeedm@nvidia.com, leon@kernel.org,
	tariqt@nvidia.com, mbloch@nvidia.com, andrew+netdev@lunn.ch,
	davem@davemloft.net, edumazet@kernel.org, pabeni@redhat.com,
	daniel.zahka@gmail.com, willemdebruijn.kernel@gmail.com,
	horms@kernel.org, shuah@kernel.org, cratiu@nvidia.com,
	raeds@nvidia.com, rrameshbabu@nvidia.com,
	linux-rdma@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-kselftest@vger.kernel.org, bjorn@kernel.org,
	dtatulea@nvidia.com
Subject: Re: [PATCH net v3 2/4] psp: support ipv6 extension headers in psp_dev_rcv() decap
Date: Mon, 26 Oct 2026 17:58:05 -0700	[thread overview]
Message-ID: <20261026175805.6d4dcae5@kernel.org> (raw)
In-Reply-To: <CADh2yMyYS-PWP4912En9D6B9up6Kz-hnCthNkWot+e7N8-q7ZA@mail.gmail.com>

On Mon, 26 Oct 2026 15:05:42 -0700 Todd Bert Freed wrote:
> > The PSP ICV doesn't cover the outer IPv6 header or its extension headers.
> > An on-path attacker could take a captured PSP packet, insert one of these
> > headers, and set saddr to an address they control. This assumes the
> > device authenticates such packets, which this patch's premise implies.
> >
> > Several of those handlers reply with an ICMPv6 error that quotes the
> > packet. With default sysctls, this happens for an unrecognized routing
> > header type (type 0, for example) with segments_left != 0:
> >
> > Before this patch, all of these packets were dropped at the is_udp check.
> > Forwarding the decrypted skb itself looks blocked by
> > sk_validate_xmit_skb() ("unencrypted skb with no associated socket -
> > dropping"). That leaves the ICMP error path as the open channel.  
> 
> Agree with this finding.

If we're leaking cleartext in ICMP responses that's also a problem
for TLS offload. We should fix that, based on skb->decrypt. right?

BTW I haven't looked closely but is there no existing helper that
would give you the ability to walk the extension headers?

  reply	other threads:[~2026-10-27  0:58 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-23 23:46 [PATCH net v3 0/4] psp: fix transport mode with ipv6 extension headers Todd Freed
2026-10-23 23:46 ` [PATCH net v3 1/4] net/mlx5e: psp: tso: replace only the length in checksum seed Todd Freed
2026-10-23 23:55   ` sashiko-bot
2026-10-24 23:48   ` netdev-bot+sashiko
2026-10-27 15:16   ` Daniel Zahka
2026-10-23 23:46 ` [PATCH net v3 2/4] psp: support ipv6 extension headers in psp_dev_rcv() decap Todd Freed
2026-10-23 23:55   ` sashiko-bot
2026-10-24 23:48   ` netdev-bot+sashiko
2026-10-26 22:05     ` Todd Bert Freed
2026-10-27  0:58       ` Jakub Kicinski [this message]
2026-10-27 10:30         ` Björn Töpel
2026-10-27 17:57         ` Todd Bert Freed
2026-10-27 15:27       ` Daniel Zahka
2026-10-27 16:50         ` Todd Bert Freed
2026-10-23 23:46 ` [PATCH net v3 3/4] psp: support ipv6 extension headers in psp_dev_encapsulate() Todd Freed
2026-10-23 23:55   ` sashiko-bot
2026-10-23 23:46 ` [PATCH net v3 4/4] selftests: drv-net: psp: test ipv6 tcp socket with extension headers Todd Freed
2026-10-23 23:55   ` sashiko-bot
2026-10-24 23:48   ` netdev-bot+sashiko
2026-10-26 22:10     ` Todd Bert Freed

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=20261026175805.6d4dcae5@kernel.org \
    --to=kuba@kernel.org \
    --cc=andrew+netdev@lunn.ch \
    --cc=bjorn@kernel.org \
    --cc=borisp@nvidia.com \
    --cc=cratiu@nvidia.com \
    --cc=daniel.zahka@gmail.com \
    --cc=davem@davemloft.net \
    --cc=dtatulea@nvidia.com \
    --cc=edumazet@kernel.org \
    --cc=horms@kernel.org \
    --cc=leon@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=linux-rdma@vger.kernel.org \
    --cc=mbloch@nvidia.com \
    --cc=netdev-bot+sashiko@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=raeds@nvidia.com \
    --cc=rrameshbabu@nvidia.com \
    --cc=saeedm@nvidia.com \
    --cc=shuah@kernel.org \
    --cc=tariqt@nvidia.com \
    --cc=toddfreed@meta.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.