CVE-2025-39965
xfrm: xfrm_alloc_spi shouldn't use 0 as SPI
MEDIUM 5.5EPSS 0.2%
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.
- Affected
- Linux
- CVSS v3.1 NVD
- 5.5 MEDIUM
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H - CVSS v3.1 CNA
- 7.8 HIGH
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H - EPSS
- 0.20% chance of exploitation in the next 30 days, 9th percentile
- Published
- 2025-10-13
- Updated
- 2026-10-15
Proof-of-concept exploits (1)
- Shreyas-Penkar/CVE-2025-399659★ · 2025-10-19
Exploit collections (1)
- linux/kernelctf/CVE-2025-39965_cosgoogle/security-research
Security advisories
- https://git.kernel.org/stable/c/0baf92d0b1590b903c1f4ead75e61715e50e8146
- https://git.kernel.org/stable/c/9fcedabaae0096f712bbb4ccca6a8538af1cd1c8
- https://git.kernel.org/stable/c/a78e55776522373c446f18d5002a8de4b09e6bf7
- https://git.kernel.org/stable/c/cd8ae32e4e4652db55bce6b9c79267d8946765a9