The Linux/Unix host has one or more packages installed that are impacted by a vulnerability without a vendor supplied patch available.

  - 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. (CVE-2025-39797)

Note that Nessus relies on the presence of the package as reported by the vendor.

Detections

Analytics

Linux Distros Unpatched Vulnerability : CVE-2025-39797

high Nessus Plugin ID 264708

Version 1.15

Version 1.14

Version 1.13

Version 1.12

Version 1.11

Version 1.10

Version 1.9

Version 1.8

Version 1.1

Version 1.15 Feb 14, 2026, 1:12 AM Detection (updated detection logic) Plugin metadata Plugin Feed: 202602140112
Version 1.14 Feb 12, 2026, 3:03 PM Detection (updated detection logic) Plugin Feed: 202602121503
Version 1.13 Feb 7, 2026, 9:06 AM Detection (updated detection logic) Plugin metadata Plugin Feed: 202602070906
Version 1.12 Jan 30, 2026, 10:33 PM Detection (updated detection logic) Plugin metadata Plugin Feed: 202601302233
Version 1.11 Jan 21, 2026, 10:50 AM Detection (updated detection logic) Plugin metadata Plugin Feed: 202601211050
Version 1.10 Jan 10, 2026, 7:58 PM Detection (updated detection logic) Plugin metadata Plugin Feed: 202601101958
Version 1.9 Dec 15, 2025, 9:39 PM Detection (updated detection logic) Plugin metadata Plugin Feed: 202512152139
Version 1.8 Nov 26, 2025, 1:15 PM CVSS metrics ("CVSSv3 score" set to 7.8. "CVSSv3 vector" set to "CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H") CVSSv3 severity (based on None, severity increased from "Medium" to "High") Detection (updated detection logic) Plugin metadata Plugin Feed: 202511261315
Version 1.1 Sep 14, 2025, 2:50 PM New Plugin Feed: 202509141450