linux-cve-announce - CVE-2025-71095: net: stmmac: fix the crash issue for zero copy XDP

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: <2026011343-CVE-2025-71095-6fad@gregkh>
Date: Tue, 13 Jan 2026 16:35:54 +0100
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...nel.org>
Subject: CVE-2025-71095: net: stmmac: fix the crash issue for zero copy XDP_TX action

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

Description
===========

In the Linux kernel, the following vulnerability has been resolved:

net: stmmac: fix the crash issue for zero copy XDP_TX action

There is a crash issue when running zero copy XDP_TX action, the crash
log is shown below.

[  216.122464] Unable to handle kernel paging request at virtual address fffeffff80000000
[  216.187524] Internal error: Oops: 0000000096000144 [#1]  SMP
[  216.301694] Call trace:
[  216.304130]  dcache_clean_poc+0x20/0x38 (P)
[  216.308308]  __dma_sync_single_for_device+0x1bc/0x1e0
[  216.313351]  stmmac_xdp_xmit_xdpf+0x354/0x400
[  216.317701]  __stmmac_xdp_run_prog+0x164/0x368
[  216.322139]  stmmac_napi_poll_rxtx+0xba8/0xf00
[  216.326576]  __napi_poll+0x40/0x218
[  216.408054] Kernel panic - not syncing: Oops: Fatal exception in interrupt

For XDP_TX action, the xdp_buff is converted to xdp_frame by
xdp_convert_buff_to_frame(). The memory type of the resulting xdp_frame
depends on the memory type of the xdp_buff. For page pool based xdp_buff
it produces xdp_frame with memory type MEM_TYPE_PAGE_POOL. For zero copy
XSK pool based xdp_buff it produces xdp_frame with memory type
MEM_TYPE_PAGE_ORDER0. However, stmmac_xdp_xmit_back() does not check the
memory type and always uses the page pool type, this leads to invalid
mappings and causes the crash. Therefore, check the xdp_buff memory type
in stmmac_xdp_xmit_back() to fix this issue.

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


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

	Issue introduced in 5.13 with commit bba2556efad66e7eaa56fece13f7708caa1187f8 and fixed in 6.1.160 with commit 3f7823219407f2f18044c2b72366a48810c5c821
	Issue introduced in 5.13 with commit bba2556efad66e7eaa56fece13f7708caa1187f8 and fixed in 6.6.120 with commit 4d0ceb7677e1c4616afb96abb4518f70b65abb0d
	Issue introduced in 5.13 with commit bba2556efad66e7eaa56fece13f7708caa1187f8 and fixed in 6.12.64 with commit 45ee0462b88396a0bd1df1991f801c89994ea72b
	Issue introduced in 5.13 with commit bba2556efad66e7eaa56fece13f7708caa1187f8 and fixed in 6.18.4 with commit 5e5988736a95b1de7f91b10ac2575454b70e4897
	Issue introduced in 5.13 with commit bba2556efad66e7eaa56fece13f7708caa1187f8 and fixed in 6.19-rc4 with commit a48e232210009be50591fdea8ba7c07b0f566a13

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-71095
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:
	drivers/net/ethernet/stmicro/stmmac/stmmac_main.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/3f7823219407f2f18044c2b72366a48810c5c821
	https://git.kernel.org/stable/c/4d0ceb7677e1c4616afb96abb4518f70b65abb0d
	https://git.kernel.org/stable/c/45ee0462b88396a0bd1df1991f801c89994ea72b
	https://git.kernel.org/stable/c/5e5988736a95b1de7f91b10ac2575454b70e4897
	https://git.kernel.org/stable/c/a48e232210009be50591fdea8ba7c07b0f566a13