vulnti.work

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: Duplica…

High CVSS 7.8
CVECVE-2025-39965
First seen2026-07-31 00:31 UTC
Disclosed2025-10-13 14:15 UTC
Last updated2026-07-31 00:31 UTC
Channel statusauto

Summary

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.

In-depth triage · Auto channel

No in-depth report has been generated yet (DR-003 v2 AI pipeline is under construction).

Affected products

  • :

Sources

  • NVD DATABASE

Original Links

Timeline

  1. nvd_ingest NVD