CVE-2025-39965 - CVE House
Back to Database
Status published Unknown CVE-2025-39965

xfrm: xfrm_alloc_spi shouldn't use 0 as SPI

Vulnerability Description

In the Linux kernel, the following vulnerability has been resolved: xfrm: xfrm_alloc_spi shouldn't use 0 as SPI 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.

Impact Analysis

Refer to official advisory for detailed impact metrics.

Remediation

Ensure systems are updated to the latest vendor-supplied patch levels.

THREAT MONITOR

Am I Vulnerable?

Launch our assessment wizard to check if your infrastructure is exposed to • CVE-2025-39965

Credits & Attribution

No credits recorded in the NVD database.

References

More from Linux

View All →
CVE-2025-71315
drm/vkms: Convert to DRM's vblank timer
Unknown 0
CVE-2025-71314
drm/panthor: Recover from panthor_gpu_flush_caches() failures
Unknown 0
CVE-2025-71313
PCI: endpoint: Add missing NULL check for alloc_workqueue()
Unknown 0
CVE-2025-71312
fs/ntfs3: fix ntfs_mount_options leak in ntfs_fill_super()
Unknown 0
CVE-2025-71311
fs/ntfs3: Initialize new folios before use
Unknown 0

Affected Vendor

Affected Software

Linux
Vulnerable Versions:
3d8090bb53424432fa788fe9a49e8ceca74f0544, 2fc5b54368a1bf1d2d74b4d3b8eea5309a653e38, 29e9158f91f99057dbd35db5e8674d93b38549fe, 94f39804d891cffe4ce17737d295f3b195bc7299, c67d4e7a8f90fb6361ca89d4d5c9a28f4e935e47, 6.15.11, 6.6.103, 6.12.43, 6.16.2

Timeline

Official Publish: October 13th, 2025
Last Modified: May 23rd, 2026
Added to House: July 22nd, 2026

CVSS Vectors

No vector data available

Weaknesses (CWE)

No CWE data available

MITRE ATT&CK TTPs

No associated TTPs found for this vulnerability.