From: Steffen Klassert <steffen.klassert@secunet.com>
To: Michael Bommarito <michael.bommarito@gmail.com>
Cc: Herbert Xu <herbert@gondor.apana.org.au>,
"David S . Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Evan Nimmo <evan.nimmo@alliedtelesis.co.nz>,
<netdev@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH net] xfrm: ah: use skb_to_full_sk in async output callbacks
Date: Wed, 20 May 2026 08:59:05 +0200 [thread overview]
Message-ID: <ag1budVqQmjiowDH@secunet.com> (raw)
In-Reply-To: <20260515154531.1386683-1-michael.bommarito@gmail.com>
On Fri, May 15, 2026 at 11:45:31AM -0400, Michael Bommarito wrote:
> When AH output is offloaded to an asynchronous crypto provider
> (hardware accelerators such as AMD CCP, or a forced-async software
> shim used for testing), the digest completion fires
> ah_output_done() / ah6_output_done() on a workqueue. The egress
> skb at that point may have been originated by a TCP listener
> sending a SYN-ACK, which sets skb->sk to a request_sock via
> skb_set_owner_edemux(); it may also have been originated by an
> inet_timewait_sock retransmit. Neither is a full struct sock, and
> passing the raw skb->sk to xfrm_output_resume() then forwards a
> non-full socket through the rest of the xfrm output chain.
>
> xfrm_output_resume() and its downstream consumers expect a full
> sk where they dereference at all. The natural egress path
> through ah_output_done() does not crash today because the
> consumers that read past sock_common are either gated by
> sk_fullsock() or short-circuit on flags that are clear on a fresh
> request_sock; an exhaustive walk of the 50 most plausible
> consumers under sch_fq, dev_queue_xmit, netfilter, tc-egress and
> cgroup-egress BPF found no current unguarded deref. The bug is
> still a real type confusion that future consumer changes could
> turn into a memory-corruption primitive.
>
> This is the same bug class fixed for ESP in commit 1620c88887b1
> ("xfrm: Fix the usage of skb->sk"). Apply the analogous fix to
> AH: convert skb->sk to a full socket pointer (or NULL) via
> skb_to_full_sk() before handing it to xfrm_output_resume().
>
> The same async AH callbacks were touched recently for an
> independent ESN-related ICV layout bug in commit ec54093e6a8f
> ("xfrm: ah: account for ESN high bits in async callbacks"); the
> sk type-confusion addressed here is orthogonal. This patch is
> part of an ongoing audit of the AH callback paths; an ah_output
> ihl-validation hardening series is also currently under review on
> netdev.
>
> Reproduced under UML + KASAN + lockdep with a forced-async
> hmac(sha1) shim that registers at priority 9999 and wraps the
> sync in-tree hmac-sha1-lib. With the shim loaded, ah_output_done
> runs on every SYN-ACK egress through a transport-mode AH SA and
> skb->sk arrives as a request_sock (TCP_NEW_SYN_RECV); after this
> patch, xfrm_output_resume() receives the listener (the result of
> sk_to_full_sk()) and consumer derefs land on full-sock fields as
> intended.
>
> Fixes: 9ab1265d5231 ("xfrm: Use actual socket sk instead of skb socket for xfrm_output_resume")
> Cc: stable@vger.kernel.org
> Assisted-by: Claude:claude-opus-4-7
> Signed-off-by: Michael Bommarito <michael.bommarito@gmail.com>
Applied to the ipsec tree, thanks!
prev parent reply other threads:[~2026-05-20 6:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-15 15:45 [PATCH net] xfrm: ah: use skb_to_full_sk in async output callbacks Michael Bommarito
2026-05-20 6:59 ` Steffen Klassert [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=ag1budVqQmjiowDH@secunet.com \
--to=steffen.klassert@secunet.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=evan.nimmo@alliedtelesis.co.nz \
--cc=herbert@gondor.apana.org.au \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michael.bommarito@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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