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.
Fix
Public exploits 1
- Shreyas-Penkar/CVE-2025-39965 PoC on GitHub
Each line links to the index that lists it, never to exploit code. Exploit-DB's "verified" and a Metasploit rank of good or better count as verified; a PoC-in-GitHub entry is a repository's claim.
Patch, vendor advisory and mitigation references on NVD 4
- https://git.kernel.org/stable/c/0baf92d0b1590b903c1f4ead75e61715e50e8146 Patch
- https://git.kernel.org/stable/c/9fcedabaae0096f712bbb4ccca6a8538af1cd1c8 Patch
- https://git.kernel.org/stable/c/a78e55776522373c446f18d5002a8de4b09e6bf7 Patch
- https://git.kernel.org/stable/c/cd8ae32e4e4652db55bce6b9c79267d8946765a9 Patch
Every line above is quoted from NVD, CISA, Microsoft, the vendor's own advisory or DISA; nothing is generated.
Change history 1
- First seenCVSS 5.5 · linuxNVD modified 2026-10-15 22:18
Affected (CPE criteria) 8
cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*cpe:2.3:o:linux:linux_kernel:6.17:rc1:*:*:*:*:*:*cpe:2.3:o:linux:linux_kernel:6.17:rc2:*:*:*:*:*:*cpe:2.3:o:linux:linux_kernel:6.17:rc3:*:*:*:*:*:*cpe:2.3:o:linux:linux_kernel:6.17:rc4:*:*:*:*:*:*cpe:2.3:o:linux:linux_kernel:6.17:rc5:*:*:*:*:*:*cpe:2.3:o:linux:linux_kernel:6.17:rc6:*:*:*:*:*:*cpe:2.3:o:linux:linux_kernel:6.17:rc7:*:*:*:*:*:*
References 4
- https://git.kernel.org/stable/c/0baf92d0b1590b903c1f4ead75e61715e50e8146 Patch
- https://git.kernel.org/stable/c/9fcedabaae0096f712bbb4ccca6a8538af1cd1c8 Patch
- https://git.kernel.org/stable/c/a78e55776522373c446f18d5002a8de4b09e6bf7 Patch
- https://git.kernel.org/stable/c/cd8ae32e4e4652db55bce6b9c79267d8946765a9 Patch