Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2025-39965xfrm: xfrm_alloc_spi shouldn't use 0 as SPI

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.

Timeline

  1. ID reserved

    By Linux

  2. · 6 months later

    Published

  3. · 13 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2025-39965, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1High7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
NVDNVD · Modified3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.20% · top 90% of all CVEs (18 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: total
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.8.

Affected products

  • Linux · Linux

    • affected 3d8090bb53424432fa788fe9a49e8ceca74f0544 – < 0baf92d0b1590b903c1f4ead75e61715e50e8146
    • affected 2fc5b54368a1bf1d2d74b4d3b8eea5309a653e38 – < 9fcedabaae0096f712bbb4ccca6a8538af1cd1c8
    • affected 29e9158f91f99057dbd35db5e8674d93b38549fe – < a78e55776522373c446f18d5002a8de4b09e6bf7
    • affected 94f39804d891cffe4ce17737d295f3b195bc7299 – < cd8ae32e4e4652db55bce6b9c79267d8946765a9
    • affected fb58962aa3b9359988c7b5b15a971fd9ad5b0ecd
    • affected c67d4e7a8f90fb6361ca89d4d5c9a28f4e935e47
    • affected 6.1.191 – < 6.2
    • affected 6.15.11 – < 6.16
  • Linux · Linux

    • affected 6.6.103 – < 6.6.109
    • affected 6.12.43 – < 6.12.50
    • affected 6.16.2 – < 6.16.10

References

References4

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2025-39965 badge
[![CVE-2025-39965](https://cveledger.app/badge/CVE-2025-39965.svg)](https://cveledger.app/cve/CVE-2025-39965)

Record last updated .