Tracker / CVE-2025-39965
CVE-2025-39965
High 7.8
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.
Affected products and versions
| linux | linux_kernel |
|---|---|
| linux | linux_kernel · 6.12.43 → 6.12.50 |
| linux | linux_kernel · 6.15.11 → 6.16 |
| linux | linux_kernel · 6.16.2 → 6.16.10 |
| linux | linux_kernel · 6.6.103 → 6.6.109 |
Analysis
This page is not indexable yet.Until it carries original analysis — what it actually exposes, how to check in two minutes whether a system was touched, what to do if it was — the page stays noindex. The database decides that, not the template.