CVE-2025-39965 (GCVE-0-2025-39965)
Vulnerability from cvelistv5
Published
2025-10-13 13:48
Modified
2025-10-13 13:48
Severity ?
VLAI Severity ?
EPSS score ?
Summary
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.
References
Impacted products
{ "containers": { "cna": { "affected": [ { "defaultStatus": "unaffected", "product": "Linux", "programFiles": [ "net/xfrm/xfrm_state.c" ], "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git", "vendor": "Linux", "versions": [ { "lessThan": "0baf92d0b1590b903c1f4ead75e61715e50e8146", "status": "affected", "version": "3d8090bb53424432fa788fe9a49e8ceca74f0544", "versionType": "git" }, { "lessThan": "9fcedabaae0096f712bbb4ccca6a8538af1cd1c8", "status": "affected", "version": "2fc5b54368a1bf1d2d74b4d3b8eea5309a653e38", "versionType": "git" }, { "lessThan": "a78e55776522373c446f18d5002a8de4b09e6bf7", "status": "affected", "version": "29e9158f91f99057dbd35db5e8674d93b38549fe", "versionType": "git" }, { "lessThan": "cd8ae32e4e4652db55bce6b9c79267d8946765a9", "status": "affected", "version": "94f39804d891cffe4ce17737d295f3b195bc7299", "versionType": "git" }, { "status": "affected", "version": "c67d4e7a8f90fb6361ca89d4d5c9a28f4e935e47", "versionType": "git" } ] }, { "defaultStatus": "unaffected", "product": "Linux", "programFiles": [ "net/xfrm/xfrm_state.c" ], "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git", "vendor": "Linux", "versions": [ { "lessThan": "6.6.109", "status": "affected", "version": "6.6.103", "versionType": "semver" }, { "lessThan": "6.12.50", "status": "affected", "version": "6.12.43", "versionType": "semver" }, { "lessThan": "6.16.10", "status": "affected", "version": "6.16.2", "versionType": "semver" } ] } ], "cpeApplicability": [ { "nodes": [ { "cpeMatch": [ { "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*", "versionEndExcluding": "6.6.109", "versionStartIncluding": "6.6.103", "vulnerable": true }, { "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*", "versionEndExcluding": "6.12.50", "versionStartIncluding": "6.12.43", "vulnerable": true }, { "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*", "versionEndExcluding": "6.16.10", "versionStartIncluding": "6.16.2", "vulnerable": true }, { "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*", "versionStartIncluding": "6.15.11", "vulnerable": true } ], "negate": false, "operator": "OR" } ] } ], "descriptions": [ { "lang": "en", "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nxfrm: xfrm_alloc_spi shouldn\u0027t use 0 as SPI\n\nx-\u003eid.spi == 0 means \"no SPI assigned\", but since commit\n94f39804d891 (\"xfrm: Duplicate SPI Handling\"), we now create states\nand add them to the byspi list with this value.\n\n__xfrm_state_delete doesn\u0027t remove those states from the byspi list,\nsince they shouldn\u0027t be there, and this shows up as a UAF the next\ntime we go through the byspi list." } ], "providerMetadata": { "dateUpdated": "2025-10-13T13:48:31.033Z", "orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "shortName": "Linux" }, "references": [ { "url": "https://git.kernel.org/stable/c/0baf92d0b1590b903c1f4ead75e61715e50e8146" }, { "url": "https://git.kernel.org/stable/c/9fcedabaae0096f712bbb4ccca6a8538af1cd1c8" }, { "url": "https://git.kernel.org/stable/c/a78e55776522373c446f18d5002a8de4b09e6bf7" }, { "url": "https://git.kernel.org/stable/c/cd8ae32e4e4652db55bce6b9c79267d8946765a9" } ], "title": "xfrm: xfrm_alloc_spi shouldn\u0027t use 0 as SPI", "x_generator": { "engine": "bippy-1.2.0" } } }, "cveMetadata": { "assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "assignerShortName": "Linux", "cveId": "CVE-2025-39965", "datePublished": "2025-10-13T13:48:31.033Z", "dateReserved": "2025-04-16T07:20:57.149Z", "dateUpdated": "2025-10-13T13:48:31.033Z", "state": "PUBLISHED" }, "dataType": "CVE_RECORD", "dataVersion": "5.1", "vulnerability-lookup:meta": { "nvd": "{\"cve\":{\"id\":\"CVE-2025-39965\",\"sourceIdentifier\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"published\":\"2025-10-13T14:15:34.910\",\"lastModified\":\"2025-10-14T19:36:29.240\",\"vulnStatus\":\"Awaiting Analysis\",\"cveTags\":[],\"descriptions\":[{\"lang\":\"en\",\"value\":\"In the Linux kernel, the following vulnerability has been resolved:\\n\\nxfrm: xfrm_alloc_spi shouldn\u0027t use 0 as SPI\\n\\nx-\u003eid.spi == 0 means \\\"no SPI assigned\\\", but since commit\\n94f39804d891 (\\\"xfrm: Duplicate SPI Handling\\\"), we now create states\\nand add them to the byspi list with this value.\\n\\n__xfrm_state_delete doesn\u0027t remove those states from the byspi list,\\nsince they shouldn\u0027t be there, and this shows up as a UAF the next\\ntime we go through the byspi list.\"}],\"metrics\":{},\"references\":[{\"url\":\"https://git.kernel.org/stable/c/0baf92d0b1590b903c1f4ead75e61715e50e8146\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"},{\"url\":\"https://git.kernel.org/stable/c/9fcedabaae0096f712bbb4ccca6a8538af1cd1c8\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"},{\"url\":\"https://git.kernel.org/stable/c/a78e55776522373c446f18d5002a8de4b09e6bf7\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"},{\"url\":\"https://git.kernel.org/stable/c/cd8ae32e4e4652db55bce6b9c79267d8946765a9\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"}]}}" } }
Loading…
Loading…
Sightings
Author | Source | Type | Date |
---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or seen somewhere by the user.
- Confirmed: The vulnerability is confirmed from an analyst perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
- Patched: This vulnerability was successfully patched by the user reporting the sighting.
- Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
- Not confirmed: The user expresses doubt about the veracity of the vulnerability.
- Not patched: This vulnerability was not successfully patched by the user reporting the sighting.
Loading…
Loading…