From: patchwork-bot+netdevbpf@kernel.org
To: Steffen Klassert <steffen.klassert@secunet.com>
Cc: davem@davemloft.net, kuba@kernel.org,
herbert@gondor.apana.org.au, netdev@vger.kernel.org
Subject: Re: [PATCH 1/2] xfrm: xfrm_alloc_spi shouldn't use 0 as SPI
Date: Tue, 23 Sep 2025 00:10:08 +0000 [thread overview]
Message-ID: <175858620800.1201993.18439475539235124519.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250922073512.62703-2-steffen.klassert@secunet.com>
Hello:
This series was applied to netdev/net.git (main)
by Steffen Klassert <steffen.klassert@secunet.com>:
On Mon, 22 Sep 2025 09:34:52 +0200 you wrote:
> From: Sabrina Dubroca <sd@queasysnail.net>
>
> x->id.spi == 0 means "no SPI assigned", but since commit
> 94f39804d891 ("xfrm: Duplicate SPI Handling"), we now create states
> and add them to the byspi list with this value.
>
> __xfrm_state_delete doesn't remove those states from the byspi list,
> since they shouldn't be there, and this shows up as a UAF the next
> time we go through the byspi list.
>
> [...]
Here is the summary with links:
- [1/2] xfrm: xfrm_alloc_spi shouldn't use 0 as SPI
https://git.kernel.org/netdev/net/c/cd8ae32e4e46
- [2/2] xfrm: fix offloading of cross-family tunnels
https://git.kernel.org/netdev/net/c/91d8a53db219
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2025-09-23 0:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-22 7:34 [PATCH 0/2] pull request (net): ipsec 2025-09-22 Steffen Klassert
2025-09-22 7:34 ` [PATCH 1/2] xfrm: xfrm_alloc_spi shouldn't use 0 as SPI Steffen Klassert
2025-09-23 0:10 ` patchwork-bot+netdevbpf [this message]
2025-09-22 7:34 ` [PATCH 2/2] xfrm: fix offloading of cross-family tunnels Steffen Klassert
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=175858620800.1201993.18439475539235124519.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=steffen.klassert@secunet.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.