PoC Monitor
← All CVEs
CVE-2025-39965published 13 Oct 2025 13:48 UTCData: JSON · API

Linux

xfrm: xfrm_alloc_spi shouldn't use 0 as SPI

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.

First public PoC 4.2 daysafter publication · 17 Oct 2025
Public PoCs11 on GitHub
CVSS7.8high · scored by CNA
CISA KEV Not listednot known exploited

Affected versions and mitigation

From the CVE record and the vendor's references.

Affected

Linux Linux
  • >= 3d8090bb53424432fa788fe9a49e8ceca74f0544, < 0baf92d0b1590b903c1f4ead75e61715e50e8146
  • >= 2fc5b54368a1bf1d2d74b4d3b8eea5309a653e38, < 9fcedabaae0096f712bbb4ccca6a8538af1cd1c8
  • >= 29e9158f91f99057dbd35db5e8674d93b38549fe, < a78e55776522373c446f18d5002a8de4b09e6bf7
  • >= 94f39804d891cffe4ce17737d295f3b195bc7299, < cd8ae32e4e4652db55bce6b9c79267d8946765a9
  • fb58962aa3b9359988c7b5b15a971fd9ad5b0ecd
  • c67d4e7a8f90fb6361ca89d4d5c9a28f4e935e47
  • >= 6.1.191, < 6.2
  • >= 6.15.11, < 6.16

Fixed in 0baf92d0b1590b903c1f4ead75e61715e50e8146, 9fcedabaae0096f712bbb4ccca6a8538af1cd1c8, a78e55776522373c446f18d5002a8de4b09e6bf7, cd8ae32e4e4652db55bce6b9c79267d8946765a9, 6.2, 6.16

Linux Linux
  • >= 6.6.103, < 6.6.109
  • >= 6.12.43, < 6.12.50
  • >= 6.16.2, < 6.16.10

Fixed in 6.6.109, 6.12.50, 6.16.10

Mitigation

Upgrade Linux to 0baf92d0b1590b903c1f4ead75e61715e50e8146 or 9fcedabaae0096f712bbb4ccca6a8538af1cd1c8 or a78e55776522373c446f18d5002a8de4b09e6bf7 or cd8ae32e4e4652db55bce6b9c79267d8946765a9 or 6.2 or 6.16 or later.

Upgrade Linux to 6.6.109 or 6.12.50 or 6.16.10 or later.

Timeline

Days relative to CVE publication
-2t=0+2+4+6+8CVE published13 Oct 2025 · t = 0First public PoC17 Oct 2025 · t+4.2d

First public PoC 4.2 days after publication; not in CISA KEV. First PoC: Shreyas-Penkar/CVE-2025-39965 (created 17 Oct 2025, found by us: backfilled).

PoC repositories

Found on GitHub.

1 PoCs

PoCs 1
RepositoryCreatedStarsAssessment
Shreyas-Penkar/CVE-2025-39965 17 Oct 2025 +4.2 d 10 PoC

Only PoCs count toward the first-PoC date and the characteristics below. Do not run PoC code from unknown sources.