CVE-2025-39797 Details
Description
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.
A vulnerability has been identified in the Linux kernel's XFRM (IPsec transformation) module, specifically in the handling of Security Parameter Index (SPI) values for inbound Security Associations (SAs). This issue arises when Strongswan sends an XFRM_MSG_ALLOCSPI Netlink message, which invokes the xfrm_alloc_spi() function. This function is supposed to guarantee the uniqueness of SPI values for inbound SAs. However, it can incorrectly indicate success even when the requested SPI is already in use. This flaw leads to duplicate SPIs being assigned to multiple inbound SAs, with the only distinction being their destination addresses. Such duplication creates inconsistencies during SPI lookups for inbound packets, as the lookup may return an arbitrary SA among those sharing the same SPI, potentially causing packet processing failures and drops. This issue contradicts RFC 4301, section 4.4.2, which states that a unicast SA is uniquely identified by the SPI and optionally the protocol.
Users can update to the latest version of the Linux kernel, where this vulnerability has been addressed. Instructions for updating the kernel can be found in the official Linux kernel documentation.
Metrics
CVSS 4.0 Severity and Vector Strings:
No CVSS 4.0 data is available for this CVE.
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
CISA-ADP
Assessed Nov 5, 2026References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
| URL | Source(s) | Tag(s) |
|---|---|---|
| https://git.kernel.org/stable/c/29e9158f91f99057dbd35db5e8674d93b38549fe | kernel.org | Patch |
| https://git.kernel.org/stable/c/2fc5b54368a1bf1d2d74b4d3b8eea5309a653e38 | kernel.org | Patch |
| https://git.kernel.org/stable/c/3d8090bb53424432fa788fe9a49e8ceca74f0544 | kernel.org | Patch |
| https://git.kernel.org/stable/c/94f39804d891cffe4ce17737d295f3b195bc7299 | kernel.org | Patch |
| https://git.kernel.org/stable/c/c67d4e7a8f90fb6361ca89d4d5c9a28f4e935e47 | kernel.org | Patch |
| https://git.kernel.org/stable/c/fb58962aa3b9359988c7b5b15a971fd9ad5b0ecd | kernel.org |
Weakness Enumeration
| CWE-ID | CWE Name | Source |
|---|---|---|
| NVD-CWE-noinfo | Insufficient Information to Classify Weakness | [email protected] |
Affected Products
| Product | Versions |
|---|---|
| linux linux kernel | < 6.6.103 >= 6.7, < 6.12.43 >= 6.13, < 6.15.11 >= 6.16, < 6.16.2 |
CPE
Remediation
| |
Change History
6 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Nov 5, 2026 | CVE Modified | CISA-ADP |
| Oct 30, 2026 | CVE Modified | kernel.org |
| Oct 19, 2026 | CVE Translated | [email protected] |
| Jun 17, 2026 | CVE Modified | kernel.org |
| Nov 24, 2025 | Initial Analysis | [email protected] |
| Sep 12, 2025 | New CVE Received | kernel.org |