What’s Vulnerable › Vulnerabilities
CVE-2025-71095: net: stmmac: fix the crash issue for zero copy XDP_TX action
- Severity: medium (CVSS 5.5 v3.1)
- Exploited in the wild: not listed in CISA KEV
- EPSS: 0.3% probability of exploitation in the next 30 days
- Public exploit or detection template: none known
- Published: 2026-01-13 · updated 2026-10-15
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.
Affected products
- Linux kernel: from 5.13.1 before 6.1.160; from 6.2 before 6.6.120; from 6.7 before 6.12.64; from 6.13 before 6.18.4; 5.13, 6.19-rc1, 6.19-rc2, 6.19-rc3, 6.19-rc4, 6.19-rc5 (+3) — fixed in 6.1.160, 6.12.64, 6.18.4, 6.6.120
How to fix
Upgrade to a fixed version: Linux kernel 6.1.160, 6.12.64, 6.18.4, 6.6.120. Check the vendor advisory for mitigations.
References
- https://git.kernel.org/stable/c/3f7823219407f2f18044c2b72366a48810c5c821
- https://git.kernel.org/stable/c/45ee0462b88396a0bd1df1991f801c89994ea72b
- https://git.kernel.org/stable/c/4d0ceb7677e1c4616afb96abb4518f70b65abb0d
- https://git.kernel.org/stable/c/5e5988736a95b1de7f91b10ac2575454b70e4897
- https://git.kernel.org/stable/c/a48e232210009be50591fdea8ba7c07b0f566a13
- https://cert-portal.siemens.com/productcert/html/ssa-019113.html
- https://cert-portal.siemens.com/productcert/html/ssa-457936.html
Get alerted when CVE-2025-71095 or the next vulnerability affects your stack