CVE-2025-39965
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.
How to fix
- linux linux_kernel6.6.109, 6.12.50, 6.16, 6.16.10 or later
Affected products
| Product | Affected versions | Fixed in |
|---|---|---|
| linux linux_kernel | 6.6.103 ≤ v < 6.6.109, 6.12.43 ≤ v < 6.12.50, 6.15.11 ≤ v < 6.16, 6.16.2 ≤ v < 6.16.10, 6.17 | 6.6.109, 6.12.50, 6.16, 6.16.10 |
Check your version
Choose the product and enter the version you run to see whether it falls in the affected range.
Attack Surface Management
See the assets tied to your domains, the technologies they run and known vulnerabilities in one list.