CVE-2025-39965

CVE-2025-39965

High · published October 13, 2025

CVSS v3.1
7.8
EPSS
0%
Percentile
8.9
In the wild
Unconfirmed
What it is

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.

The record
Technical detail
CVSS v3.1
7.8 · HIGH
Vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
CVSS v4.0
Not supplied
EPSS
0.00197 · 8.9th percentile
Published
2025-10-13T18:15Z
Affected products (11)
ProductVersionsFixed in
linux/linux_kernel≥ 6.6.103, < 6.6.1096.6.109
linux/linux_kernel≥ 6.12.43, < 6.12.506.12.50
linux/linux_kernel≥ 6.15.11, < 6.166.16
linux/linux_kernel≥ 6.16.2, < 6.16.106.16.10
linux/linux_kernelall versions—
linux/linux_kernelall versions—
linux/linux_kernelall versions—
linux/linux_kernelall versions—
linux/linux_kernelall versions—
linux/linux_kernelall versions—
linux/linux_kernelall versions—
References (4)
EPSS history
Timeline
  • 13 OCT 13:48Z
    xfrm: xfrm_alloc_spi shouldn't use 0 as SPI
    cvelistv5