Bug 2403546 (CVE-2025-39965) - CVE-2025-39965 kernel: xfrm: xfrm_alloc_spi shouldn't use 0 as SPI
Summary: CVE-2025-39965 kernel: xfrm: xfrm_alloc_spi shouldn't use 0 as SPI
Keywords:
Status: NEW
Alias: CVE-2025-39965
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Product Security DevOps Team
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2025-10-13 14:01 UTC by OSIDB Bzimport
Modified: 2025-10-14 23:03 UTC (History)
0 users

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)

Description OSIDB Bzimport 2025-10-13 14:01:36 UTC
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.


Note You need to log in before you can comment on or make changes to this bug.