From: Herbert Xu <herbert@gondor.apana.org.au>
To: Aakash Kumar S <saakashkumar@marvell.com>
Cc: netdev@vger.kernel.org, steffen.klassert@secunet.com,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, horms@kernel.org, akamaluddin@marvell.com
Subject: Re: [PATCH] xfrm: Duplicate SPI Handling – IPsec-v3 Compliance Concern
Date: Mon, 9 Jun 2025 12:54:30 +0800 [thread overview]
Message-ID: <aEZpBsgcdTTKr98q@gondor.apana.org.au> (raw)
In-Reply-To: <20250602181948.129956-1-saakashkumar@marvell.com>
On Mon, Jun 02, 2025 at 11:49:48PM +0530, Aakash Kumar S wrote:
>
> diff --git a/net/xfrm/xfrm_state.c b/net/xfrm/xfrm_state.c
> index 341d79ecb5c2..d0b221a4a625 100644
> --- a/net/xfrm/xfrm_state.c
> +++ b/net/xfrm/xfrm_state.c
> @@ -2550,7 +2550,6 @@ int xfrm_alloc_spi(struct xfrm_state *x, u32 low, u32 high,
> __be32 minspi = htonl(low);
> __be32 maxspi = htonl(high);
> __be32 newspi = 0;
> - u32 mark = x->mark.v & x->mark.m;
>
> spin_lock_bh(&x->lock);
> if (x->km.state == XFRM_STATE_DEAD) {
> @@ -2565,7 +2564,7 @@ int xfrm_alloc_spi(struct xfrm_state *x, u32 low, u32 high,
> err = -ENOENT;
>
> if (minspi == maxspi) {
> - x0 = xfrm_state_lookup(net, mark, &x->id.daddr, minspi, x->id.proto, x->props.family);
> + x0 = xfrm_state_lookup_byspi(net, minspi, x->props.family);
> if (x0) {
> NL_SET_ERR_MSG(extack, "Requested SPI is already in use");
> xfrm_state_put(x0);
> @@ -2576,7 +2575,7 @@ int xfrm_alloc_spi(struct xfrm_state *x, u32 low, u32 high,
> u32 spi = 0;
> for (h = 0; h < high-low+1; h++) {
> spi = get_random_u32_inclusive(low, high);
> - x0 = xfrm_state_lookup(net, mark, &x->id.daddr, htonl(spi), x->id.proto, x->props.family);
> + x0 = xfrm_state_lookup_byspi(net, htonl(spi), x->props.family);
> if (x0 == NULL) {
> newspi = htonl(spi);
> break;
The patch looks OK to me.
Acked-by: Herbert Xu <herbert@gondor.apana.org.au>
That function in general has some issues though. First of all
the SPI search is racy. We only take the lock and update the
state database after the search. That means the supposedly unique
SPI may no longer be unique.
The search for an SPI in the range is also prone to DoS attacks
if the SPI range is large and dense at the same time. That depends
on how user-space constructs the range of course.
Cheers,
--
Email: Herbert Xu <herbert@gondor.apana.org.au>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
next prev parent reply other threads:[~2025-06-09 4:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-02 18:19 [PATCH] xfrm: Duplicate SPI Handling – IPsec-v3 Compliance Concern Aakash Kumar S
2025-06-09 4:54 ` Herbert Xu [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-06-12 5:50 Aakash Kumar S
2025-06-09 6:50 Aakash Kumar S
2025-06-11 10:51 ` Steffen Klassert
2025-06-12 9:02 ` Antony Antony
2025-05-26 6:43 Aakash Kumar S
2025-05-26 8:08 ` Herbert Xu
2025-05-26 6:41 Aakash Kumar S
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=aEZpBsgcdTTKr98q@gondor.apana.org.au \
--to=herbert@gondor.apana.org.au \
--cc=akamaluddin@marvell.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=saakashkumar@marvell.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox