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.
History

Mon, 13 Oct 2025 14:00:00 +0000

Type Values Removed Values Added
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.
Title xfrm: xfrm_alloc_spi shouldn't use 0 as SPI
References

cve-icon MITRE

Status: PUBLISHED

Assigner: Linux

Published:

Updated: 2025-10-13T13:48:31.033Z

Reserved: 2025-04-16T07:20:57.149Z

Link: CVE-2025-39965

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Received

Published: 2025-10-13T14:15:34.910

Modified: 2025-10-13T14:15:34.910

Link: CVE-2025-39965

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

No data.