Answer in brief
CVE-2025-39965 records a Unknown severity vulnerability in xfrm: xfrm_alloc_spi shouldn't use 0 as SPI. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=3d8090bb53424432fa788fe9a49e8ceca74f0544 <0baf92d0b1590b903c1f4ead75e61715e50e8146 || >=2fc5b54368a1bf1d2d74b4d3b8eea5309a653e38 <9fcedabaae0096f712bbb4ccca6a8538af1cd1c8 || >=29e9158f91f99057dbd35db5e8674d93b38549fe <a78e55776522373c446f18d5002a8de4b09e6bf7 || >=94f39804d891cffe4ce17737d295f3b195bc7299 <cd8ae32e4e4652db55bce6b9c79267d8946765a9 || c67d4e7a8f90fb6361ca89d4d5c9a28f4e935e47 || >=6.15.11 <6.16 | 0baf92d0b1590b903c1f4ead75e61715e50e8146, 9fcedabaae0096f712bbb4ccca6a8538af1cd1c8, a78e55776522373c446f18d5002a8de4b09e6bf7, cd8ae32e4e4652db55bce6b9c79267d8946765a9, 6.16 |
| Linux/Linuxgeneric | >=6.6.103 <6.6.109 || >=6.12.43 <6.12.50 || >=6.16.2 <6.16.10 | 6.6.109, 6.12.50, 6.16.10 |
Published upstream
Oct 13, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
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.
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2025-39965 records a Unknown severity vulnerability in xfrm: xfrm_alloc_spi shouldn't use 0 as SPI. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=3d8090bb53424432fa788fe9a49e8ceca74f0544 <0baf92d0b1590b903c1f4ead75e61715e50e8146 || >=2fc5b54368a1bf1d2d74b4d3b8eea5309a653e38 <9fcedabaae0096f712bbb4ccca6a8538af1cd1c8 || >=29e9158f91f99057dbd35db5e8674d93b38549fe <a78e55776522373c446f18d5002a8de4b09e6bf7 || >=94f39804d891cffe4ce17737d295f3b195bc7299 <cd8ae32e4e4652db55bce6b9c79267d8946765a9 || c67d4e7a8f90fb6361ca89d4d5c9a28f4e935e47 || >=6.15.11 <6.16 | 0baf92d0b1590b903c1f4ead75e61715e50e8146, 9fcedabaae0096f712bbb4ccca6a8538af1cd1c8, a78e55776522373c446f18d5002a8de4b09e6bf7, cd8ae32e4e4652db55bce6b9c79267d8946765a9, 6.16 |
| Linux/Linuxgeneric | >=6.6.103 <6.6.109 || >=6.12.43 <6.12.50 || >=6.16.2 <6.16.10 | 6.6.109, 6.12.50, 6.16.10 |
Published upstream
Oct 13, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
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.
Quoted source text, attributed separately from HOL analysis.