linux-cve-announce - CVE-2025-39965: xfrm: xfrm_alloc

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <2025101336-CVE-2025-39965-9772@gregkh>
Date: Mon, 13 Oct 2025 15:48:36 +0200
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...nel.org>
Subject: CVE-2025-39965: xfrm: xfrm_alloc_spi shouldn't use 0 as SPI

From: Greg Kroah-Hartman <gregkh@...nel.org>

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.

The Linux kernel CVE team has assigned CVE-2025-39965 to this issue.


Affected and fixed versions
===========================

	Issue introduced in 6.6.103 with commit 3d8090bb53424432fa788fe9a49e8ceca74f0544 and fixed in 6.6.109 with commit 0baf92d0b1590b903c1f4ead75e61715e50e8146
	Issue introduced in 6.12.43 with commit 2fc5b54368a1bf1d2d74b4d3b8eea5309a653e38 and fixed in 6.12.50 with commit 9fcedabaae0096f712bbb4ccca6a8538af1cd1c8
	Issue introduced in 6.16.2 with commit 29e9158f91f99057dbd35db5e8674d93b38549fe and fixed in 6.16.10 with commit a78e55776522373c446f18d5002a8de4b09e6bf7
	Issue introduced in 6.15.11 with commit c67d4e7a8f90fb6361ca89d4d5c9a28f4e935e47

Please see https://www.kernel.org for a full list of currently supported
kernel versions by the kernel community.

Unaffected versions might change over time as fixes are backported to
older supported kernel versions.  The official CVE entry at
	https://cve.org/CVERecord/?id=CVE-2025-39965
will be updated if fixes are backported, please check that for the most
up to date information about this issue.


Affected files
==============

The file(s) affected by this issue are:
	net/xfrm/xfrm_state.c


Mitigation
==========

The Linux kernel CVE team recommends that you update to the latest
stable kernel version for this, and many other bugfixes.  Individual
changes are never tested alone, but rather are part of a larger kernel
release.  Cherry-picking individual commits is not recommended or
supported by the Linux kernel community at all.  If however, updating to
the latest release is impossible, the individual changes to resolve this
issue can be found at these commits:
	https://git.kernel.org/stable/c/0baf92d0b1590b903c1f4ead75e61715e50e8146
	https://git.kernel.org/stable/c/9fcedabaae0096f712bbb4ccca6a8538af1cd1c8
	https://git.kernel.org/stable/c/a78e55776522373c446f18d5002a8de4b09e6bf7
	https://git.kernel.org/stable/c/cd8ae32e4e4652db55bce6b9c79267d8946765a9