CVE-2025-39797

In the Linux kernel, the following vulnerability has been resolved: xfrm: Duplicate SPI Handling The issue originates when Strongswan initiates an XFRM_MSG_ALLOCSPI Netlink message, which triggers the kernel function xfrm_alloc_spi(). This function is expected to ensure uniqueness of the Security Parameter Index (SPI) for inbound Security Associations (SAs). However, it can return success even when the requested SPI is already in use, leading to duplicate SPIs assigned to multiple inbound SAs, differentiated only by their destination addresses. This behavior causes inconsistencies during SPI lookups for inbound packets. Since the lookup may return an arbitrary SA among those with the same SPI, packet processing can fail, resulting in packet drops. According to RFC 4301 section 4.4.2 , for inbound processing a unicast SA is uniquely identified by the SPI and optionally protocol. Reproducing the Issue Reliably: To consistently reproduce the problem, restrict the available SPI range in charon.conf : spi_min = 0x10000000 spi_max = 0x10000002 This limits the system to only 2 usable SPI values. Next, create more than 2 Child SA. each using unique pair of src/dst address. As soon as the 3rd Child SA is initiated, it will be assigned a duplicate SPI, since the SPI pool is already exhausted. With a narrow SPI range, the issue is consistently reproducible. With a broader/default range, it becomes rare and unpredictable. Current implementation: xfrm_spi_hash() lookup function computes hash using daddr, proto, and family. So if two SAs have the same SPI but different destination addresses, then they will: a. Hash into different buckets b. Be stored in different linked lists (byspi + h) c. Not be seen in the same hlist_for_each_entry_rcu() iteration. As a result, the lookup will result in NULL and kernel allows that Duplicate SPI Proposed Change: xfrm_state_lookup_spi_proto() does a truly global search - across all states, regardless of hash bucket and matches SPI and proto.

• https://git.kernel.org/stable/c/29e9158f91f99057dbd35db5e8674d93b38549fePatch
• https://git.kernel.org/stable/c/2fc5b54368a1bf1d2d74b4d3b8eea5309a653e38Patch
• https://git.kernel.org/stable/c/3d8090bb53424432fa788fe9a49e8ceca74f0544Patch
• https://git.kernel.org/stable/c/94f39804d891cffe4ce17737d295f3b195bc7299Patch
• https://git.kernel.org/stable/c/c67d4e7a8f90fb6361ca89d4d5c9a28f4e935e47Patch

Published

Sep 12, 2025

Last Modified

Jun 17, 2026

Status

Analyzed

• How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
• Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
• PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
• AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.

• CVE-2025-39791In the Linux kernel, the following vulnerability has been re…5.5
• CVE-2025-39792In the Linux kernel, the following vulnerability has been re…5.5
• CVE-2025-39793In the Linux kernel, the following vulnerability has been re…7.8
• CVE-2025-39794In the Linux kernel, the following vulnerability has been re…5.5
• CVE-2025-39795In the Linux kernel, the following vulnerability has been re…5.5
• CVE-2025-39796In the Linux kernel, the following vulnerability has been re…7.8
• CVE-2025-39798In the Linux kernel, the following vulnerability has been re…5.5
• CVE-2025-39799Rejected reason: This CVE ID has been rejected or withdrawn …
• CVE-2025-3980A vulnerability classified as problematic was found in wowjo…5.3
• CVE-2025-39800In the Linux kernel, the following vulnerability has been re…5.5
• CVE-2025-39801In the Linux kernel, the following vulnerability has been re…5.5
• CVE-2025-39802In the Linux kernel, the following vulnerability has been re…7.8