Riskcovery

CVE-2025-39965

xfrm: xfrm_alloc_spi shouldn't use 0 as SPI

State
Published
Severity
7.8 High
Published
Oct 13, 2025
Updated
Oct 30, 2026
Reserved
Apr 16, 2025

Read the record on cve.org

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.

Scores

CVSSScoreVectorSource
3.17.8 HighCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:HLinux

Weaknesses

The record names no weakness.

Affected Products

ProductVersions
LinuxLinux
  • 3d8090bb53424432fa788fe9a49e8ceca74f0544 to before 0baf92d0b1590b903c1f4ead75e61715e50e8146Affected
  • 2fc5b54368a1bf1d2d74b4d3b8eea5309a653e38 to before 9fcedabaae0096f712bbb4ccca6a8538af1cd1c8Affected
  • 29e9158f91f99057dbd35db5e8674d93b38549fe to before a78e55776522373c446f18d5002a8de4b09e6bf7Affected
  • 94f39804d891cffe4ce17737d295f3b195bc7299 to before cd8ae32e4e4652db55bce6b9c79267d8946765a9Affected
  • fb58962aa3b9359988c7b5b15a971fd9ad5b0ecdAffected
  • c67d4e7a8f90fb6361ca89d4d5c9a28f4e935e47Affected
  • 6.1.191 to before 6.2Affected
  • 6.15.11 to before 6.16Affected
LinuxLinux
  • 6.6.103 to before 6.6.109Affected
  • 6.12.43 to before 6.12.50Affected
  • 6.16.2 to before 6.16.10Affected

References

Every record here comes from the CVE Program’s CVE List. © 1999–2026 The MITRE Corporation. CVE is a registered trademark of The MITRE Corporation. The records are reproduced under the CVE Program terms of use.