CVE-2025-39965
Last modified
CVE-2025-39965 is a medium-severity vulnerability rated 5.5/10 on the CVSS scale. 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.. EPSS estimates a 0.18% chance of exploitation in the next 30 days.
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.
Metrics
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Affected Software
| Vendor | Product | Versions | Update |
|---|---|---|---|
| Linux | Linux Kernel | >= 6.6.103, < 6.6.109 | — |
| 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.17 | Rc1 |
References
Timeline
- Published
- Last Modified
- Status
- Analyzed
Frequently Asked Questions
What is CVE-2025-39965?
How severe is CVE-2025-39965?
How do I fix CVE-2025-39965?
Are you affected by CVE-2025-39965?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
